Security audit
Security checks for vulnerabilities and agentic risk
The skill requires confirmation for customer changes, but its setup can execute downloaded software without separate approval or integrity checks.
Review and approve the CLI installation separately before allowing this skill to run its setup commands. Check the CLI's bundled-agent-skill installation behavior and understand that OOMOL mediates access to customer data. The remote installer and hosted service implementation remain outside this artifact review; no malicious behavior was established.
The supplied code performs remote script execution from an Oomol installation endpoint, not Helcim data access. Nothing in the supplied chunk establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents and any further actions are not visible.
Piping a live HTTPS response directly into Bash executes remote code without verifying an immutable version, checksum, or signature. Compromise of the installer delivery path could enable arbitrary commands, local data theft, or persistent modifications under the invoking user's privileges; HTTPS and conditional setup reduce some exposure but do not establish artifact integrity.
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 setup workflow directs execution of downloaded shell or PowerShell code without requiring installation-specific approval or explaining that it can modify the local system with the invoking user's privileges. The missing-CLI condition limits exposure, but a Helcim data request does not necessarily authorize local software installation; the write-confirmation safeguards cover Helcim state rather than this setup 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