Security audit
Security checks for vulnerabilities and agentic risk
Kernel operations have clear approval rules, but fallback setup runs downloaded code without a separate installation approval step.
Review and approve CLI installation separately before using the fallback setup, including any installation of additional agent skills. The downloaded installers were unavailable for inspection. Kernel writes and deletions have explicit approval safeguards, and the inspected artifact contains no evidence of malicious intent.
The supplied code performs remote script execution from an Oomol endpoint rather than showing Kernel data operations. Although installation can be a supporting implementation detail, nothing supplied establishes this installer as a Kernel dependency. The downloaded script is not provided, so its further behavior cannot be determined.
Piping a live HTTPS download directly into bash executes mutable remote code with the invoking user's permissions, without version pinning or independent integrity verification. Compromise of the installer endpoint or distribution pipeline could therefore expose local files and credentials; the legitimate dependency purpose and missing-command trigger reduce exposure but do not remove that 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 missing-CLI fallback directs the agent to execute an installer that changes the local system without requiring an explanation of those changes or explicit installation approval. Its conditional nature reduces exposure, and enforcement of the declared Bash(oo *) tool restriction could block execution, but the setup instructions themselves lack a consent boundary.
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