Security audit
Security checks for vulnerabilities and agentic risk
The Grafana read operations fit the stated purpose, but setup can automatically execute an unverified remote installer.
Review and install a verified CLI version yourself before use, and retain control over additional agent skills it installs or synchronizes. Use a read-only Grafana credential and consider whether you trust OOMOL to handle the connection. The external installers and hosted connector were not verified, so this review does not establish their safety.
The supplied command performs remote script execution for an apparent CLI installation, not Grafana Cloud searches or reads. Nothing in the chunk establishes this installation as a supporting dependency for the declared purpose. The downloaded script is not provided, so its additional behavior cannot be assessed.
Piping an unpinned remote script directly into bash gives its publisher, or an attacker controlling its delivery infrastructure, code execution on the agent's host. HTTPS protects transport but does not establish artifact integrity against a compromised publisher; this is the same underlying installer vulnerability identified by SQP-2, not a separate attack chain.
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 setup instructions execute downloaded shell and PowerShell scripts immediately, without an integrity check, pinned artifact, or explicit installation approval. A compromised distribution endpoint could execute arbitrary code with the invoking user's privileges; limiting this to a missing-CLI error reduces exposure but does not make execution safe.
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