Security audit
Security checks for vulnerabilities and agentic risk
The HoneyHive workflow is coherent, but its setup instructions can execute unverified downloaded code without separate user approval.
Review and approve CLI installation separately, using a verified version and checking its effects on installed agent skills. OOMOL mediates HoneyHive access and receives action payloads. Keep the skill's explicit approvals for writes and deletion. The bundled skill was fully inspected, but downloaded installer contents and the credential-handling implementation remain unverified.
The supplied command executes an external installer and shows no HoneyHive interaction. Nothing in the supplied material establishes Oomol installation as a supporting requirement for HoneyHive, so this is an undeclared capability involving an inconsistent resource. The downloaded script's further behavior cannot be determined from this chunk.
The command pipes a mutable remote script directly into bash without version pinning, integrity verification, or review. A compromised installer host or release pipeline could therefore execute arbitrary code with the agent's local privileges; HTTPS protects transport but does not establish that the script itself is trustworthy.
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 the agent to execute downloaded shell or PowerShell code without explicitly obtaining approval for local installation and system changes. Although triggered only when the CLI is missing, this expands a HoneyHive data request into local code execution with the agent's privileges, and the write-confirmation rules cover HoneyHive state rather than this installation.
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