Security audit
Security checks for vulnerabilities and agentic risk
The Snipcart read operations fit its purpose, but setup can execute unverified software without asking you first.
Review and approve CLI installation separately before allowing this skill to run. Prefer a verified, fixed CLI release and control its automatic skill synchronization; the publisher documents OO_SKILLS_SYNC_DISABLED=1 for disabling startup synchronization. Connect only the intended Snipcart account and understand that OOMOL mediates access to customer and order data. The remote installer and server-side implementation were not verified; no malicious behavior was established.
The supplied command performs remote installer execution, not Snipcart searching or reading. Nothing in the supplied chunk establishes that this installation is a supporting dependency for Snipcart functionality. The downloaded script's contents and any further effects are not available for assessment.
Piping the HTTPS response directly into Bash executes mutable remote code without version pinning, integrity verification, or an opportunity to review the complete script first. HTTPS protects transport but not against a compromised publisher or distribution endpoint, which could deliver code that steals accessible credentials or modifies local files; the adjacent PowerShell command 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
The setup instructions direct an agent to execute downloaded shell or PowerShell code without explaining that this grants the installer the executing user's privileges or requiring explicit installation approval. The missing-CLI condition limits exposure, but it still allows a read-oriented task to trigger system changes and potentially arbitrary code execution if the installer source is compromised.
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