Security audit
Security checks for vulnerabilities and agentic risk
The StatusCake workflow is coherent, but its setup can automatically execute an unverified remote installer.
Review and approve CLI installation separately, preferably using a verified release. Confirm whether it will install or update other agent skills, and ensure you trust OOMOL to handle your StatusCake connection. The skill appropriately requires approval for account changes and deletion; the Review verdict concerns setup execution and its unresolved effects, not evidence of malicious intent.
The supplied code installs software from Oomol rather than performing StatusCake operations. Nothing in the supplied chunk establishes that this installation is a supporting dependency for the declared purpose. The downloaded script's contents are not provided, so its further behavior cannot be determined.
Piping the HTTPS installer directly into bash executes whatever content the endpoint returns without a pinned version, integrity verification, or review. If the distribution endpoint or its publishing pipeline is compromised, an attacker could execute code with the agent's privileges and access local files or credentials; the Windows installation command has the same underlying risk.
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 setup instructs the agent to execute remotely downloaded shell or PowerShell code without requiring review or explicit user approval for installation and system changes. Restricting this workflow to a missing CLI reduces exposure, but a routine dependency error can still trigger execution with the agent's local 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