Security audit
Security checks for vulnerabilities and agentic risk
The Keen IO actions have clear safeguards, but setup can execute unverified remote code and the CLI can silently install persistent agent skills.
Review the CLI setup before enabling this skill. Prefer a verified release installed under your control, and understand that Keen IO requests pass through OOMOL. To prevent the documented startup skill synchronization, set OO_SKILLS_SYNC_DISABLED=1 before invoking the CLI. Keep the required confirmation for event writes. No malicious behavior was established, but the remote installers could not be inspected and their future contents are not fixed.
The supplied command performs remote script installation rather than any visible Keen IO operation. Nothing in the supplied chunk establishes this installer as a supporting dependency for the declared functionality. The downloaded script's contents and subsequent effects are not available for assessment.
The supplied chunk only performs an authentication command; it contains no Keen IO resource references or data operations. Authentication could support the declared purpose, but this chunk provides no evidence of that connection and instead implements a standalone login flow.
The curl-to-bash command immediately executes mutable remote content without verifying its integrity or authenticity beyond HTTPS transport. Although the domain is relevant to the documented CLI dependency, compromise of that endpoint or release pipeline could lead to local arbitrary code execution; this is the same underlying installation risk identified by SQP-2.
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 directs execution of downloaded shell and PowerShell scripts without an explicit installation approval gate or integrity verification. If the installer endpoint or its delivery pipeline is compromised, attacker-controlled code can execute with the invoking user's privileges; triggering only when the CLI is absent limits exposure but does not remove the risk.
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