Security audit
Security checks for vulnerabilities and agentic risk
The billing lookups fit the stated purpose, but setup can execute unverified remote installers without a separate approval step.
Review setup before installing. Independently verify and approve the CLI installation, and decide whether its automatic skill synchronization is acceptable. The publisher documents OO_SKILLS_SYNC_DISABLED as a control in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Connect only the intended Maxio account and consider OOMOL's access to its billing data. Remote installer contents remain unverified; no malicious behavior was established in the bundled artifact.
The supplied command performs remote script execution, not the declared Maxio data-access function. Nothing in the chunk establishes that this installer is a supporting dependency for Maxio access. The downloaded script's contents and any further effects are not available for assessment.
Piping the HTTPS response directly into Bash executes whatever code the installation endpoint returns, without prior inspection or integrity verification. A compromised endpoint or release pipeline could therefore turn a read-only billing request into local arbitrary code execution; this is the same underlying installation risk identified by SQP-2, not an independent exploit.
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 instructs an agent to execute downloaded shell or PowerShell code without explicit installation approval, a pinned version, or artifact verification. If the distribution endpoint is compromised, that code could access local files and credentials or modify the system with the executing user's privileges; the missing-CLI condition limits exposure but does not remove the risk.
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