Security audit
Security checks for vulnerabilities and agentic risk
The CaptainBI workflow fits its purpose, but setup can execute unverified remote code without asking first.
Review and approve a fixed CLI release before allowing setup. Check its automatic skill synchronization and disable it if unwanted. Connect only the intended CaptainBI account and understand that OOMOL mediates access to its business data. The bundled instructions were fully inspected; remote installer and connector behavior remain unverified. No malicious behavior was established.
The supplied command performs remote software installation rather than searching or reading CaptainBI data. Nothing in the provided chunk establishes that this installer is a necessary supporting component for CaptainBI access. The downloaded script's contents are not supplied, so its further effects cannot be determined.
Piping a mutable remote installer directly into bash executes its contents with the invoking user's privileges, without a pinned version or independent integrity verification. If the distribution endpoint or release pipeline is compromised, the installer could access local secrets or modify files; HTTPS and the legitimate dependency relationship do not eliminate that 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 fallback directs the agent to execute a remote installer without explaining that this runs third-party code locally or requiring explicit installation approval. Triggering setup only when the CLI is missing reduces exposure, but a request to read CaptainBI data does not itself authorize arbitrary local installation and its potential filesystem or environment changes.
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