Security audit
Security checks for vulnerabilities and agentic risk
The Anrok read workflow fits its purpose, but setup directs the agent to execute unverified remote installers without a separate approval step.
Review and install the CLI separately before enabling this skill, and require approval before any fallback installer runs. Connecting Anrok allows OOMOL to mediate access to sensitive business data. The remote installer contents and actual installation effects were unavailable for verification; no malicious behavior was established in the bundled skill.
The supplied code executes an Oomol-hosted installer and contains no Anrok interaction or data-reading functionality. Nothing supplied establishes this installer as a supporting dependency for the declared purpose. The downloaded script's contents are unavailable, so its further effects cannot be determined.
Piping an HTTPS response directly into bash executes mutable remote content without establishing its integrity or allowing inspection before execution. HTTPS protects transport but not against compromise of the vendor's distribution infrastructure; this is the same underlying installation risk as SQP-2, not a separate attack chain.
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 directs execution of remotely downloaded shell or PowerShell scripts without review, integrity verification, or explicit user approval for system changes. If the distribution endpoint or installer is compromised, following this setup instruction could execute attacker-controlled code with the user's privileges; the missing-CLI condition reduces exposure but does not eliminate it.
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