Security audit
Security checks for vulnerabilities and agentic risk
The Sanity workflow has clear approval controls, but its automatic setup runs unverified remote code and omits broader changes the CLI can make to installed agent skills.
Review and approve CLI installation separately, preferably using a verified, fixed release. Check its bundled-skill installation settings; the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables) documents OO_SKILLS_SYNC_DISABLED for disabling startup skill synchronization. Connect only the Sanity access needed and retain approval checks for mutations. The remote installer payload remains unverified.
The supplied command performs remote installer execution rather than any visible Sanity data operation. Nothing in the supplied chunk establishes that installing Oomol supports the declared Sanity functionality. The remote script's contents are not provided, so its further behavior cannot be determined.
Piping a remotely fetched script directly into Bash executes whatever the endpoint returns with the agent process's privileges, without version pinning or independent integrity verification. Compromise of the installer distribution path could therefore expose local files and credentials or modify the system; HTTPS and the legitimate dependency relationship do not eliminate 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 first obtaining explicit approval for local software installation or explaining its effects. A user requesting Sanity data operations may not have authorized arbitrary local code execution; limiting installation to a missing-CLI error reduces exposure but does not establish that authorization.
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