Security audit
Security checks for vulnerabilities and agentic risk
The Whop reading workflow fits its purpose, but setup can execute an unverified remote installer without clear user control over broader local changes.
Review and install the CLI yourself before enabling this skill, and connect Whop with only the permissions needed for your reads. Check whether you want bundled skills synchronized into other agents; the [CLI command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED to disable that behavior. The complete bundled artifact was inspected, but the remote installers were unavailable, so their exact local changes remain unknown.
The supplied command executes an external installer, an undeclared capability not established as necessary for Whop access. The code contains no Whop search or read operation. The remote script's contents are not supplied, so its further effects cannot be determined.
Piping a remotely downloaded script directly into Bash executes its contents with the agent process's local privileges, without a pinned version or independent integrity verification. Compromise of the distribution endpoint could therefore enable local data theft or modification; the PowerShell alternative has the same download-and-execute risk, although neither command itself demonstrates malicious intent.
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 fallback directs the agent to execute an installer without first obtaining approval for local software installation and its system changes. A request to read Whop data does not necessarily authorize executing third-party code; limiting setup to a missing dependency reduces exposure but does not establish consent.
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