Security audit
Security checks for vulnerabilities and agentic risk
Review recommended because setup can run downloaded installation code without asking, although CloudConvert changes require approval.
Review and approve CLI installation separately, using a pinned and verified release. Consider whether additional agent skills should be synchronized; the documented OO_SKILLS_SYNC_DISABLED setting disables that behavior. OOMOL mediates the connected account's operations. CloudConvert writes and deletions have explicit approval safeguards, and no malicious behavior was established in the bundled artifact.
The supplied chunk performs remote installer execution rather than CloudConvert operations. Nothing in the chunk establishes that this installer is a supporting dependency for CloudConvert. The downloaded script's contents and further effects are not visible.
Piping an HTTPS response directly into bash executes mutable remote content without version pinning or independent integrity verification. Compromise of the installer host or publishing pipeline could therefore execute attacker-controlled code with the user's permissions; the legitimate OOMOL dependency explains the destination but does not remove this 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 fallback directs the agent to execute a remote installer without explicit approval for local code execution or installation changes. Although this is a legitimate dependency setup step and only occurs when the CLI is missing, it expands a CloudConvert request into execution of externally supplied code with the invoking user's permissions.
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