Security audit
Security checks for vulnerabilities and agentic risk
The address-validation workflow is reasonable, but its setup can execute unchecked remote code and introduce undisclosed changes to other agent skills.
Review setup before installing. Use a verified, fixed CLI release and disable startup skill synchronization before its first invocation using OO_SKILLS_SYNC_DISABLED=1, as documented in the [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Addresses pass through OOMOL, and the actual remote installers and released binary remain unverified.
The only supplied command executes an installer from a non-Google domain, without any demonstrated connection to address validation. This is an undeclared installation capability rather than an established supporting implementation detail. The remote script's contents and any further effects cannot be determined from this chunk.
The setup instructions pipe a remotely fetched, mutable script directly into Bash without verifying a pinned version or integrity; the PowerShell alternative has the same problem. If the distribution endpoint or its publishing infrastructure is compromised, following these instructions could execute attacker-controlled code with the agent process's privileges and expose local files or credentials. The legitimate dependency-installation context and missing-command prerequisite reduce suspicion of malicious intent but do not remove the 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
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