Security audit
Security checks for vulnerabilities and agentic risk
The AeroLeads lookup fits its purpose, but setup runs unverified remote installers and the required CLI has broader effects on installed agent skills than this skill explains.
Review the setup before use. Install a verified CLI release yourself and decide whether to disable its startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1 before invoking it. OOMOL mediates the requested contact lookups, which may consume credit. The bundled instructions were fully reviewed, but the remote installers and hosted connector implementation were not verified.
The supplied code contains no AeroLeads search or read operations. Instead, it executes a remote installation script from an unrelated domain, with no demonstrated connection to the declared purpose. The remote script's contents and resulting actions are not provided, so its specific effects cannot be determined.
The supplied code only initiates login and contains no AeroLeads-specific operation. Authentication could be a supporting implementation detail, but this chunk provides no connection between the login command and the declared AeroLeads functionality.
Piping the HTTPS response directly into Bash executes mutable remote content without verifying its integrity or allowing prior inspection. Compromise of the distribution endpoint or its supply chain could therefore lead to arbitrary local code execution; this is the same underlying installation risk identified by SQP-2, not evidence of an intentionally malicious domain.
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 fallback instructs execution of remotely fetched shell and PowerShell installers without explicit installation approval, integrity verification, or review. If followed, a compromised installer source could execute arbitrary code with the agent's local privileges; the missing-CLI condition narrows exposure but does not eliminate it.
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