Security audit
Security checks for vulnerabilities and agentic risk
The KoboToolbox workflow has clear safeguards, but its setup instructions can trigger unverified software installation without separate user approval.
Review and approve CLI installation separately, preferably using a pinned, verified release. Check its automatic skill synchronization before running it. Connect only the KoboToolbox account and data you intend OOMOL to process, and retain the stated confirmations for writes and deletions. The remote installer and hosted connector implementation were not verified; no malicious behavior was established.
The supplied chunk installs software from a non-KoboToolbox domain rather than performing any visible KoboToolbox operation. Although dependency installation can be a supporting implementation detail, the chunk provides no evidence connecting this installer to the declared purpose. The remote script's contents and any further effects cannot be determined from the supplied code.
Piping the installer URL directly into Bash executes whatever content the endpoint supplies with the agent's local privileges, without pinning or independent integrity verification. HTTPS protects transport but does not prevent a compromised publisher or hosting endpoint from supplying malicious code; the legitimate CLI dependency and conditional fallback reduce exposure but do not remove this supply-chain 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 remote installation scripts without explicit user approval or disclosure of local-system changes. Although restricted to a setup failure, this expands a KoboToolbox task into local code execution; the write/destructive confirmation rules cover KoboToolbox state, not installation.
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