Security audit
Security checks for vulnerabilities and agentic risk
The Statsig read workflow is coherent, but its setup instructions can trigger remote code execution without an explicit installation approval step.
Review the setup before installing. Use a reviewed CLI release and require approval before software or additional agent skills are installed. Connecting Statsig entrusts its API key and requested data to OOMOL; use narrowly scoped credentials. The live installers and hosted connector were not verified.
The declared purpose concerns reading and searching Statsig data, but the code executes an Oomol-hosted installer. No relationship to Statsig is established in the supplied chunk, so this is an inconsistent resource and an undeclared execution capability rather than a demonstrated supporting implementation detail. The installer’s downstream actions cannot be determined from this chunk.
Piping a mutable remote script directly into bash executes its contents without prior review or independent integrity verification; the PowerShell alternative has the same issue. If the distribution endpoint or release process is compromised, the installer could run arbitrary commands with the invoking user's privileges, exposing local files and credentials despite Statsig tokens being managed server-side.
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 missing-CLI recovery path instructs the agent to execute a remote installer without explaining its local effects or requiring explicit installation approval. Although conditional setup reduces exposure, a Statsig read request could unexpectedly trigger local software installation and execution under the user's account.
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