Security audit
Security checks for vulnerabilities and agentic risk
Customer-data changes require approval, but setup directs the agent to run downloaded installers without a separate approval or verification step.
Review and approve the CLI installation separately before allowing setup, including any automatic agent-skill changes. Use narrowly scoped Checkout.com access and retain approval for customer changes or deletion. OOMOL mediates the account connection and requests; the downloaded installers and server-side implementation were not verified.
The supplied command installs software from an unrelated service and shows no Checkout.com functionality or connection establishing it as a supporting implementation detail. The remote script's contents are not supplied, so its further behavior cannot be determined.
The command pipes a mutable remote script directly into Bash without verifying a pinned artifact or its authenticity beyond HTTPS transport. If the distribution infrastructure is compromised, attacker-controlled code could run with the agent's permissions and access local data or credentials; the legitimate dependency context and missing-CLI condition reduce exposure but do not eliminate this 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 instructs the agent to install software after a missing-command error without first obtaining approval for local system changes. Although this is legitimate dependency setup and only conditionally triggered, a Checkout.com request does not itself authorize executing an installer with the agent's local permissions.
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