Security audit
Security checks for vulnerabilities and agentic risk
The Woot features fit their purpose, but setup instructs the agent to execute downloaded installation code without a clear approval step.
Review setup before installing. Verify and install the CLI yourself, require approval for installation changes, and review its automatic skill synchronization. The [publisher's command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED for disabling startup synchronization. OOMOL mediates Woot requests and credentials. The artifact shows no malicious intent, but downloaded installer code and the hosted backend were not verified.
The supplied chunk performs remote installer execution rather than searching or reading Woot data. It contains no Woot-specific operations or evidence establishing the installer as a supporting dependency. The remote script's contents are not supplied, so its additional effects cannot be determined.
The supplied code only initiates authentication and shows no connection to Woot or implementation of the declared functionality. Authentication could be a supporting step in a larger implementation, but the supplied chunk provides no evidence of that relationship.
Piping an unpinned HTTPS response directly into Bash executes whatever code the installation endpoint returns, without verifying an immutable artifact or trusted signature. Compromise of the endpoint or its publishing pipeline could lead to local data theft or modification under the user's account; this overlaps with the setup-workflow finding rather than representing 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 fallback setup instructs the agent to execute downloaded shell or PowerShell scripts without an explicit user-approval step or artifact verification. A compromised distribution endpoint could thereby execute arbitrary code with the invoking user's privileges; although conditional setup reduces exposure, it exceeds the system changes normally expected from a Woot read request.
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