Security audit
Security checks for vulnerabilities and agentic risk
The Raygun workflow includes clear safeguards, but its setup directs the agent to execute downloaded installation code without a separate review or approval step.
Review and approve a verified oo CLI installation separately before using the skill. Raygun requests pass through OOMOL, and changes or deletion should retain the stated approval requirements. The downloaded installer and installed CLI were not verified in this review.
The supplied code performs remote script installation rather than any visible Raygun operation. Nothing in the chunk establishes that this installer is a supporting dependency for Raygun. The downloaded script's contents are not supplied, so its further effects cannot be determined.
Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
- `get_deployment` — Retrieve a Raygun deployment by identifier.
- `get_error_group` — Retrieve a Raygun error group by identifier.
- `get_latest_deployment` — Retrieve the latest deployment for a Raygun application.
- `list_applications` — List Raygun applications available to the personal access token.
- `list_deployments` — List deployments for a Raygun application.
- `list_error_groups` — List crash reporting error groups for a Raygun application.
- `update_deployment` — Update a Raygun deployment. [write]
Piping a remotely fetched, unpinned script directly into Bash executes its contents with the invoking account's permissions without prior integrity verification or review. HTTPS and the legitimate OOMOL dependency reduce some risks but do not protect against a compromised distribution endpoint or altered installer; the PowerShell alternative has the same execution pattern.
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 install software on the local system after a missing-command error without requiring informed user approval. Although conditional and relevant to the workflow, installation crosses a different authorization boundary from performing a Raygun action and may modify executables, configuration, or shell startup files.
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