Security audit
Security checks for vulnerabilities and agentic risk
Review is needed because setup executes unverified downloaded scripts and omits the CLI’s documented changes to other agent skills.
Use a reviewed, pinned CLI installation before enabling this skill. Disable startup skill synchronization with OO_SKILLS_SYNC_DISABLED=1 if you do not want broader agent changes. Consider whether submitted HTML/CSS is suitable for processing through OOMOL, and retain the required approval steps for image creation and deletion. The remote installers and CLI binary were not audited.
The supplied command performs remote script execution rather than HTML/CSS to Image operations. Nothing in the supplied chunk establishes that installing the Oomol CLI is a supporting requirement for the declared service. The downloaded script's contents and any subsequent effects are not available for assessment.
The curl-to-Bash command immediately executes whatever script the remote endpoint returns, without version pinning or independent integrity verification. HTTPS protects transport but does not prevent a compromised publisher or hosting endpoint from supplying malicious code; this overlaps the setup vulnerability identified by SQP-2 rather than representing a separate attack path.
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 setup instructions pipe downloaded scripts directly into Bash or PowerShell without verifying their integrity or obtaining explicit installation approval. If the installer endpoint or delivery infrastructure is compromised, this can execute attacker-controlled code with the invoking user's permissions; restricting setup to a missing-CLI error reduces exposure but does not remove that risk.
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