Security audit
Security checks for vulnerabilities and agentic risk
The FullContact workflow is coherent, but its automatic setup executes unverified remote code without a clear user approval step.
Review setup before enabling this skill. Install a reviewed, version-pinned CLI separately and decide whether to allow its agent-skill synchronization. Only submit personal identifiers you intend OOMOL and FullContact to process. The bundled file shows no malicious payload, but the external installer and hosted connector implementations were not verified.
The supplied code performs remote installer execution, not FullContact searching or data retrieval. Nothing in the chunk establishes that this installation supports the declared FullContact functionality, so it cannot be treated as a demonstrated supporting implementation detail. The downloaded script's further behavior is not visible.
The setup instructions pipe a mutable remote script directly into Bash without a pinned version, independently verified integrity, or review; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could execute attacker-controlled code with the agent's local privileges and expose accessible files or credentials. The missing-CLI prerequisite limits when this occurs, and the declared oo-only Bash permission does not authorize the installer, but neither makes the installation guidance safe.
oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):
curl -fsSL https://cli.oomol.com/install.sh | bash # macOS / Linux
The workflow instructs the agent to execute connector actions and declares all untagged actions safe to run directly. Person-enrichment and verification requests transmit personal identifiers through OOMOL to FullContact, but the safety section addresses only state changes and does not warn about this disclosure of personal data.
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
- **`OOMOL_INSUFFICIENT_CREDIT`** — OOMOL billing stop. Recharge at `https://console.oomol.com/billing/token-recharge` before retrying.
- **HTTP 402 without `OOMOL_INSUFFICIENT_CREDIT`** — the third-party account itself has no active plan or credit. Report the provider error message as is; do not ask the user to recharge OOMOL.
## Resources