Security audit
Security checks for vulnerabilities and agentic risk
The Waitwhile actions have clear approval safeguards, but setup runs unverified downloaded code and the dependency can silently install additional agent skills.
Review and verify the CLI installer before allowing setup. OOMOL will mediate access to your Waitwhile customer data. Its documented startup skill synchronization extends beyond this integration; disable it before first use if unwanted, using OO_SKILLS_SYNC_DISABLED as described in the [publisher's documentation](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md#environment-variables). Continue requiring approval for customer changes and deletions. The remote installer remains uninspected.
The declared purpose concerns Waitwhile data operations, but the supplied code executes an Oomol-hosted installer. Nothing in the chunk establishes this installer as a supporting dependency for Waitwhile. The remote script's contents and effects cannot be determined from the supplied code.
The setup command pipes a remotely fetched, mutable script directly into Bash without verifying its contents or integrity; the PowerShell alternative uses the same download-and-execute pattern. Compromise of the distribution endpoint could execute attacker-controlled code with the agent process's permissions, potentially exposing local credentials or modifying files. The legitimate dependency and missing-CLI condition reduce execution frequency but do not establish script trust.
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
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