Security audit
Security checks for vulnerabilities and agentic risk
The Check functions fit the stated purpose, but setup can execute unverified remote code and introduce broader persistent changes to agent skills.
Review and approve the CLI installation separately before allowing automatic setup. OOMOL mediates Check requests and receives their inputs. If you only want this integration, review or disable the CLI's broader skill synchronization; the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED. The downloaded installers were not inspected, so their exact local effects remain uncertain.
The supplied command performs remote script execution rather than searching or reading Check data. Nothing in the supplied chunk establishes that installing this external CLI is a supporting requirement for Check access. The downloaded script's contents and further effects cannot be determined from this chunk.
Piping a live HTTPS download directly into bash executes whatever the installer endpoint supplies, without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. If the distribution endpoint or delivery pipeline is compromised, attacker-controlled code could run with the agent process's local privileges and access its files and credentials.
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
A missing CLI causes the workflow to instruct installation without first obtaining approval for executing remote code and changing the local environment. This expands a Check data-reading request into software installation; the conditional setup trigger limits exposure but does not establish user 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