Security audit
Security checks for vulnerabilities and agentic risk
The phone-call workflow requires confirmation, but setup instructs the agent to execute unchecked remote installers without separate approval.
Review and install the CLI separately before enabling this skill, using a verified release where available. OOMOL mediates account access, and outbound calls require confirmation of their exact details. The bundled instructions were fully inspected, but the external installers and CLI implementation were not verified; the Review verdict concerns setup control, with no artifact-backed evidence of malicious intent.
The supplied code performs remote installer execution rather than Pod AI operations. Installing a dependency could be a supporting implementation detail, but nothing supplied establishes that the Oomol installer supports Pod AI. The downloaded script's further behavior cannot be determined from this chunk.
Piping a mutable remote installer directly into Bash executes whatever the endpoint returns with the invoking user's privileges, without prior inspection or artifact verification. A compromised distribution endpoint could therefore execute arbitrary local code; HTTPS and a relevant vendor domain do not eliminate that supply-chain risk. This overlaps SQP-2, and the declared Bash(oo *) restriction may prevent execution if strictly enforced.
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 setup instructs the agent to execute downloaded shell or PowerShell scripts without explicit approval, integrity verification, or an explanation of the resulting system changes. Restricting setup to a missing CLI reduces exposure, but installing software remains a separate trust decision from authorizing a Pod AI action.
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