Security audit
Security checks for vulnerabilities and agentic risk
The Airbrake functions fit their stated purpose, but setup can execute unchecked downloaded software without separate approval.
Review and approve the CLI installation separately, use a verified release, and consider disabling automatic agent-skill synchronization. Connect only an appropriately limited Airbrake account and understand that OOMOL mediates access. The remote installers and hosted implementation were not verified; the supplied artifact does not establish malicious intent.
The supplied code installs or runs externally supplied software rather than searching or reading Airbrake data. No connection between this installer and the declared Airbrake functionality is established. Executing a remote installation script is a materially different, undeclared capability; the script's further behavior cannot be determined from this chunk.
The command pipes a mutable network response directly into Bash without pinning or independently verifying its contents; the PowerShell alternative has the same execution pattern. HTTPS protects transport but does not prevent a compromised distribution endpoint or malicious installer update from executing code with the agent's privileges and accessing locally available data.
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
A missing CLI triggers instructions to install software without first obtaining approval for local system changes or execution of remote code. Although this fallback is conditional, an ordinary Airbrake read request could consequently lead to arbitrary code execution with the agent process's privileges, exceeding the request's expected scope.
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