Security audit
Security checks for vulnerabilities and agentic risk
Freshstatus changes require approval, but the CLI setup and its broader, persistent changes to agent skills need review.
Review and approve the CLI installation separately, preferably using a verified, pinned release. Decide whether to permit its cross-agent skill synchronization; the publisher documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. Connect only the Freshstatus account you intend to use and retain approval for changes and deletions. The downloaded installers and remote service implementation were not audited.
The supplied code's sole behavior is fetching and executing an installer from an unrelated service. Nothing in the chunk establishes that this is a supporting dependency for Freshstatus or implements the declared functionality. The downloaded script's further behavior cannot be determined from the supplied code.
The command pipes a mutable HTTPS response directly into bash without verifying the installer artifact. HTTPS protects transport but not against compromise of the distribution infrastructure or publisher account, so malicious replacement content could run with the invoking user's privileges; this is the same underlying installation risk identified by SQP-2.
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 fallback instructs execution of downloaded shell or PowerShell code without an explicit installation approval step, integrity verification, or explanation of local changes. Although installing a required CLI is legitimate and conditional, it crosses from Freshstatus operations into local code execution; compromised installer content could execute with the invoking user's 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