Security audit
Security checks for vulnerabilities and agentic risk
The incident-reading workflow is coherent, but its automatic setup can execute changing remote code without clearly explaining or confirming local changes.
Review setup before installing. Install a verified CLI release separately, approve its local changes, and review or disable automatic skill synchronization. Connect incident.io with read-only permissions where available, and consider whether your incident data may be processed through OOMOL. The read workflow is consistent with its purpose; the remote installers' exact behavior remains unverified.
The supplied chunk performs remote script execution rather than incident.io searches or reads. Although installing a required dependency could be a supporting implementation detail, the supplied content establishes no relationship between this installer and the declared incident.io functionality. The downloaded script's contents and any resulting system changes are not visible.
Piping a live HTTPS response directly into bash executes remotely supplied code without a pinned version or independent integrity verification; the PowerShell alternative has the same risk. Although the host is relevant to the documented dependency and installation is conditional, compromise of the distribution endpoint could lead to arbitrary code execution and access to files or credentials available to the agent.
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 an agent to execute installation scripts without explaining their local effects or requiring approval for changes outside the read-only incident.io workflow. Execution is conditional on the CLI being missing, which reduces exposure, but an installer can modify files and execute commands with the agent's operating-system privileges.
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