Security audit
Security checks for vulnerabilities and agentic risk
Review the setup first: it immediately executes downloaded software and can change skills used by other agents without explaining those changes.
Install and verify oo separately before allowing this skill to run setup. Review its cross-agent skill changes; the publisher documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. Keep approval requirements for destructive commands. The only bundled artifact was fully inspected, but the remote installers and hosted connector implementation remain unverified.
The supplied command performs remote installer execution and contains no visible HARPA AI operations. Nothing supplied establishes the Oomol installer as a supporting dependency for HARPA AI, so its resource access and installation behavior materially differ from the declared purpose. The downloaded script's further behavior cannot be determined from this chunk.
The supplied chunk only invokes a CLI login command and contains no HARPA AI operations or explicit connection to HARPA AI. Authentication could support the declared purpose, but the supplied code does not establish that relationship or implement the described functionality.
The setup command streams a mutable remote script directly into Bash without verifying its integrity or reviewing it; the PowerShell alternative has the same issue. If the distribution endpoint or installer supply chain is compromised, attacker-controlled code would execute with the agent process's local permissions, potentially exposing files and credentials. The missing-CLI condition limits exposure, but the legitimate setup purpose and HTTPS do not establish the script's 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