Security audit
Security checks for vulnerabilities and agentic risk
The VBOUT workflow requires approval for data changes, but its setup can execute remote installation code and make lasting changes to agent skills without separate approval.
Review and approve the oo CLI installation separately before use. Consider disabling automatic skill synchronization with OO_SKILLS_SYNC_DISABLED=1, as documented in the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Keep the required confirmations for contact changes and deletion. The remote installer and hosted connector code remain unverified; no malicious behavior was established in the bundled artifact.
The supplied chunk performs remote installer execution rather than VBOUT operations. Nothing in the supplied code establishes that this installer is a supporting dependency for VBOUT functionality. The downloaded script is not provided, so its further behavior cannot be assessed.
The command pipes a mutable remote script directly into bash without a pinned version or independently verified integrity; the PowerShell alternative uses the same download-and-execute pattern. If the installer distribution is compromised, attacker-controlled code could run with the agent's local permissions and access available files or credentials. HTTPS and the setup-only condition reduce some exposure but do not prevent a compromised publisher or installer endpoint.
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 missing-CLI fallback directs the agent to execute a remote installer without explaining its system effects or obtaining installation-specific approval. Although limited to a setup failure, this can turn a VBOUT data request into local software installation; the existing confirmation rules address VBOUT writes, not local system changes.
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