Security audit
Security checks for vulnerabilities and agentic risk
Store changes require approval, but automatic setup runs an unverified installer whose documented effects extend to other agent skills.
Review the CLI installation before allowing automatic setup. Use a reviewed release, check which agent skills it installs or updates, and consider disabling startup skill synchronization using the publisher's documented controls. OOMOL mediates store access; approve exact product changes and deletion targets. The remote installer and connector implementation were not verified.
The supplied command executes an external installer rather than performing BigCommerce operations. Nothing in the code establishes that this installation supports the declared purpose. The downloaded script's contents are not provided, so its additional behavior cannot be determined.
The setup instruction pipes a mutable remotely downloaded script directly into a shell without verifying its contents, signature, or expected digest. Compromise of the distribution endpoint could execute attacker-controlled code with the agent process's permissions; the missing-CLI prerequisite limits exposure but does not mitigate execution risk, and the PowerShell alternative has the same weakness.
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