Security audit
Security checks for vulnerabilities and agentic risk
This BugBug integration needs review because its fallback setup executes downloaded code without verification or explicit installation approval.
Install a reviewed, pinned CLI yourself before use and require approval for host changes. Review its automatic skill synchronization; the documented OO_SKILLS_SYNC_DISABLED=1 setting disables startup sync. Confirm that you trust OOMOL with the connected BugBug account and retain confirmation for test runs. Remote installer contents and server-side connector behavior were not verified.
The supplied command executes an Oomol-hosted installation script, with no demonstrated connection to BugBug. Although dependency installation can be a supporting implementation detail, the provided chunk establishes no such relationship. The remote script's contents and any further effects are not visible.
Piping a mutable remote script directly into bash executes its contents with the agent process's privileges without an independent integrity check or review. A compromised distribution endpoint could therefore enable credential theft or host modification; the OOMOL domain is relevant to this dependency, but HTTPS alone does not protect against compromised publisher infrastructure. The PowerShell example has the same risk, although actual execution depends on tool permissions.
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 downloaded installer code without explicitly obtaining approval for software installation or explaining the resulting system changes. The missing-command prerequisite reduces exposure, but a request to operate BugBug does not necessarily authorize executing an installer on the host.
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