Security audit
Security checks for vulnerabilities and agentic risk
Ticketmaster changes require approval, but setup runs unverified downloaded software and omits the dependency’s broader changes to agent skills.
Review and install a fixed CLI release before use instead of letting setup execute a changing remote script. Consider disabling its additional skill synchronization; the publisher documents OO_SKILLS_SYNC_DISABLED=1 for that purpose. Confirm every Ticketmaster change and be comfortable using OOMOL to handle requests and connected credentials. The complete bundled artifact was inspected, but the remote installer and hosted connector implementation remain unverified. No malicious intent is established. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)
The supplied chunk installs external software rather than performing Ticketmaster operations. It provides no evidence that this installer is a supporting dependency for the declared Ticketmaster functionality. The downloaded script's contents and further effects are not visible in the supplied code.
The setup command streams a remote script directly into Bash without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the distribution endpoint could therefore execute arbitrary code with the agent process's permissions, potentially exposing local files and credentials. Conditional setup reduces exposure, and the declared Bash(oo *) restriction may block installation if strictly enforced, but neither makes this installation guidance safe.
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