Security audit
Security checks for vulnerabilities and agentic risk
The OpenHands integration is coherent, but its setup directs the agent to execute downloaded installers without separate user approval or integrity checks.
Review and approve CLI setup separately before allowing the agent to run it; prefer a pinned, verified release. Consider the publisher-documented installation of additional agent skills and OOMOL's role in handling connected-account access. Keep the skill's exact-payload confirmation for OpenHands changes. The external installers were unavailable for inspection.
The supplied code performs remote installer execution, with no visible OpenHands integration or data operations. Nothing supplied establishes that installing software from cli.oomol.com is a supporting implementation detail of the declared OpenHands functionality. The downloaded script's contents and further effects cannot be determined from this chunk.
The command pipes a mutable remote script directly into Bash without a pinned version or independent integrity verification. Compromise of the installer endpoint or its publishing pipeline could execute arbitrary code with the user's permissions, exposing local files and credentials; HTTPS and the legitimate setup context do not eliminate that 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 setup instructions direct execution of downloaded shell and PowerShell scripts without explaining that they run with the invoking user's permissions or requesting installation-specific approval. Limiting setup to a missing CLI reduces exposure, but it does not prevent an agent from treating remote code execution as routine recovery.
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