Security audit
Security checks for vulnerabilities and agentic risk
Review is needed because this Zeplin reading skill can trigger remote software installation and broader changes to installed agent skills.
Review and approve CLI installation separately, and understand that OOMOL handles access to your connected Zeplin data. To prevent automatic changes to other agents' skills, the CLI documents setting OO_SKILLS_SYNC_DISABLED=1 for every invocation. The remote installer and hosted connector implementation remain unverified. See the [documented environment controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables).
The supplied command shows no Zeplin access or data-reading behavior. It instead executes an external installation script, with no demonstrated connection to the declared Zeplin purpose. The downloaded script's contents and resulting system changes are not visible in the supplied chunk.
The command streams a mutable remote script directly into Bash without a pinned version or independent integrity verification; the PowerShell alternative has the same execution pattern. Compromise of the installer distribution infrastructure could execute attacker-controlled code with the agent process's permissions, potentially exposing accessible files and credentials. HTTPS and the legitimate setup context reduce some risks but do not establish the integrity of the code being executed.
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 installation without explaining that downloaded code will execute locally or requiring explicit approval for that change. Although setup is conditional and relevant to the task, a request to read Zeplin data does not necessarily authorize installing software or modifying the local environment.
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