Security audit
Security checks for vulnerabilities and agentic risk
Box operations have clear approval safeguards, but setup can execute unverified remote code and introduce broader agent changes without clear user control.
Review setup before enabling this skill. Install a verified CLI release separately and check its automatic skill synchronization settings; the documented OO_SKILLS_SYNC_DISABLED control disables that synchronization. OOMOL will mediate Box access and downloaded content. Keep the existing write and deletion confirmations. The installer contents could not be inspected, so their exact local changes remain uncertain.
The supplied chunk performs no visible Box operations and instead executes an installer from a non-Box domain. Although dependency installation can be a supporting implementation detail, this chunk establishes no connection between the Oomol installer and the declared Box functionality. The downloaded script's contents are not supplied, so its further behavior cannot be assessed.
Piping an HTTPS response directly into bash executes mutable remote content without verifying an expected release or reviewing the script. HTTPS protects transport but does not prevent a compromised distribution service from supplying malicious code, which could access local files or credentials under the current user's permissions.
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 directs the agent to execute downloaded shell or PowerShell code without an integrity check or explicit approval for local software installation. A compromised distribution endpoint could execute arbitrary code with the invoking user's privileges; the missing-CLI condition limits exposure but does not make the installation safe.
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