Security audit
Security checks for vulnerabilities and agentic risk
The Store Leads workflow fits its purpose, but its fallback setup executes an unverified remote installer and leaves broader agent changes unexplained.
Review setup before installing. Prefer a separately verified CLI installation and explicitly control any installation or synchronization of other agent skills. Connect only the Store Leads access you intend OOMOL to use. The installer and downloaded binary were not audited; no malicious behavior was established.
The supplied code performs remote software installation, not Store Leads data access. Although installing a dependency can be a supporting implementation detail, this chunk establishes no connection between the Oomol installer and the declared Store Leads functionality. The downloaded script's contents are not supplied, so its additional effects cannot be determined.
The supplied chunk performs only a login operation rather than the declared Store Leads functionality. Authentication could be a supporting implementation detail if linked to Store Leads, but the supplied code establishes no such link and contains no implementation of the advertised data access.
The fallback pipes a mutable remote script directly into bash without version pinning, integrity verification, or inspection; the adjacent PowerShell alternative has the same issue. If the distribution endpoint or installer is compromised, execution can access files and credentials or modify the host with the agent's privileges; conditional execution and HTTPS reduce exposure but do not establish script integrity.
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
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