Security audit
Security checks for vulnerabilities and agentic risk
The contact lookup workflow fits its purpose, but automatic setup executes unverified downloaded code without clear user control.
Review and install the CLI separately before use, and decide whether its automatic agent-skill synchronization is acceptable. Submit only identifiers you intend OOMOL and Reverse Contact to process. The remote installers and exact installed dependency were not inspected, so their full local effects remain uncertain.
The supplied code performs remote installation rather than searching or reading Reverse Contact data. Nothing in the chunk establishes the Oomol installer as a supporting dependency for Reverse Contact. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
The supplied chunk performs only a login operation; it contains no Reverse Contact search or data-reading behavior. Authentication could be a supporting implementation detail, but this chunk provides no connection between the oo login flow and the declared service.
The fallback installation pipes a mutable remote script directly into Bash without verifying its contents or integrity; the PowerShell alternative uses the same download-and-execute pattern. If the distribution endpoint or delivery infrastructure is compromised, an attacker can execute code with the agent's local privileges and potentially access credentials or files. The missing-CLI condition limits when this occurs, but HTTPS alone does not prevent distribution-side compromise.
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, including person enrichment using an email, name, or company context. Although it identifies Reverse Contact and OOMOL, it never warns that the supplied personal identifiers will be transmitted to those services, and instead labels untagged actions as safe to run directly.
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