Security audit
Security checks for vulnerabilities and agentic risk
This ContactOut helper needs review because its setup runs unverified remote code and its CLI can change other installed agent skills.
Review and install the CLI separately before use. Its documented startup synchronization can be disabled with OO_SKILLS_SYNC_DISABLED=1. Share only lookup identifiers you intend OOMOL and ContactOut to receive, and consider usage charges. No malicious payload was established, but the remote installer was unavailable for inspection.
The supplied code performs remote script execution, not ContactOut searching or reading. Nothing in the chunk establishes that the Oomol installer is a supporting dependency for ContactOut, and its installation behavior is not disclosed in the description. The downloaded script's contents and further effects cannot be determined from this chunk.
The setup instructions pipe a mutable remote script directly into Bash without inspection, version pinning, or independent integrity verification; the PowerShell alternative has the same issue. If the installation endpoint or its delivery infrastructure is compromised, attacker-controlled code would execute with the agent process's local permissions. Restricting installation to a missing-CLI error reduces exposure but does not remove this supply-chain risk.
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 execution workflow instructs the agent to submit action payloads through OOMOL to ContactOut; these payloads can contain email addresses, LinkedIn URLs, or other personal identifiers. The safety section addresses state changes but does not warn that read-only lookups also disclose submitted data to external services.
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
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
## Resources
- ContactOut homepage: https://contactout.com
- API documentation: https://api.contactout.com/