Security audit
Security checks for vulnerabilities and agentic risk
The Autobound integration is coherent, but its setup fallback can execute an unverified remote installer without clear user approval.
Review and install the CLI separately before enabling this skill, and prevent automatic execution of its remote installer. Check the CLI's automatic skill-installation behavior and the Autobound permissions granted through OOMOL. Installer effects remain unverified; the concern is insufficient control over setup, with no artifact evidence establishing malicious intent.
The supplied code performs remote installer execution, not Autobound searching or reading. Nothing in the supplied chunk establishes this installation as a supporting dependency for Autobound. The downloaded script's contents are not provided, so its further effects cannot be assessed.
The command pipes a mutable remote script directly into Bash without verifying its integrity or reviewing it before execution; the PowerShell alternative has the same weakness. Compromise of the installation endpoint or its delivery infrastructure could execute attacker-controlled code with the agent's local permissions, potentially exposing accessible files and credentials; HTTPS alone does not protect against a compromised publisher.
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
A missing CLI triggers instructions to install software by executing a downloaded script, without requiring informed user approval for local system changes. The fallback-only condition limits exposure, but a request to read Autobound data does not itself authorize installing and executing software on the user's machine.
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