Security audit
Security checks for vulnerabilities and agentic risk
Certifier actions have clear approval controls, but setup can execute remote code and introduce broader changes to your agents without adequately explaining them.
Review and approve CLI installation separately before proceeding. OOMOL documents OO_SKILLS_SYNC_DISABLED=1 to disable startup skill synchronization; verify that control for your chosen release. Keep the skill's approval requirement for issuing and sending credentials, and consider whether you trust OOMOL with Certifier access and recipient data. The remote installer and backend implementation remain unverified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables)
The supplied command executes an installer hosted by Oomol, with no demonstrated connection to Certifier. Although dependency installation can be a supporting implementation detail, the supplied chunk establishes no such relationship and shows only unrelated remote code execution. The downloaded script's contents and further effects are not available for assessment.
Piping an unpinned remote script directly into Bash executes whatever the installation endpoint returns, without an independent integrity check or review. HTTPS and the legitimate dependency context reduce suspicion of malicious intent, but compromise of the distribution endpoint could yield arbitrary code execution with access to local files and credentials; the PowerShell alternative has the same 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 tells the agent to execute remotely downloaded shell or PowerShell code without first obtaining approval for software installation or explaining the resulting system changes. Restricting setup to a missing-CLI error reduces exposure, but a routine Certifier request could still trigger code execution with the agent's local privileges; the declared Bash tool restriction may constrain execution if enforced.
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