Security audit
Security checks for vulnerabilities and agentic risk
Short Menu changes require approval, but missing-software setup directs the agent to execute a remote installer without asking first.
Review and install the oo CLI separately before enabling this skill, including its effects on other installed agent skills. Connect only the intended Short Menu account and retain confirmation for changes and deletions. OOMOL processes connector requests and manages service credentials. The bundled instructions were fully inspected, but external installers and live connector implementations were not verified; no malicious behavior was established.
The supplied command installs remote software; it does not show any Short Menu data operations. Nothing in the supplied content establishes this installer as a supporting dependency for Short Menu, so its behavior is materially different from the declared purpose. The installer contents are not provided, so its further effects cannot be determined.
Piping a remotely fetched script directly into Bash executes whatever the endpoint returns with the agent process's local privileges, without a pinned version or independent integrity verification. A compromised distribution endpoint could therefore lead to local data theft or modification; the PowerShell alternative has the same risk. The documented vendor relationship and missing-CLI prerequisite reduce suspicion of malicious intent but do not eliminate the supply-chain exposure.
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 instructs the agent to install software after a missing-command error without first explaining local system changes or obtaining approval. Authorization to manage Short Menu data does not necessarily authorize executing an installer on the local machine, although the conditional fallback limits when this risk arises.
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