Security audit
Security checks for vulnerabilities and agentic risk
The Countdown API workflow fits its purpose, but setup can execute unverified remote installers without a separate user approval step.
Review and approve CLI installation separately before using this skill, preferably using a pinned release with verified integrity. Check whether that CLI release installs additional agent skills. Countdown API access through OOMOL is disclosed and coherent, but the remote installer and service implementation were not verified.
The supplied command performs remote script execution for an installer, not Countdown API searching or reading. Nothing in the supplied chunk establishes that this installation is a supporting dependency for Countdown API access. The downloaded script's further behavior cannot be determined from the provided code.
The supplied code only invokes a login command; it contains no Countdown API search or read operation and establishes no connection between oo and Countdown API. Authentication could be a supporting implementation detail, but the supplied chunk does not demonstrate that relationship.
The command pipes a mutable network response directly into Bash without a pinned version, independently verified integrity, or review before execution. Compromise of the distribution endpoint or its publishing pipeline could therefore execute attacker-controlled code with the agent process's privileges; HTTPS alone does not protect against those compromises.
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
On a missing-command error, the skill directs installation through remotely downloaded shell or PowerShell code without first requiring informed approval or explaining host changes. Although setup is relevant and conditional, authorizing a data lookup does not inherently authorize arbitrary installer execution, which could modify files or access credentials with the executing 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