Security audit
Security checks for vulnerabilities and agentic risk
A Mindbody lookup can trigger remote software installation without a separate approval step, so the setup deserves review.
Review and approve CLI installation separately before allowing automatic setup. Prefer a pinned, integrity-verified release, and check its installation effects. The publisher documents OO_SKILLS_SYNC_DISABLED for preventing startup writes to agent skill directories in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). OOMOL mediates access to your connected account. The supplied skill shows no malicious behavior, but the remote installer remains unverified.
The supplied code performs remote installer execution rather than Mindbody data access. Although dependency installation can be a supporting implementation detail, this chunk establishes no connection between the Oomol installer and the declared functionality. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
The command pipes a mutable network response directly into Bash without a pinned version or independently verified integrity; the Windows alternative uses the same download-and-execute pattern. Compromise of the distribution endpoint or delivery infrastructure could therefore execute arbitrary code and access local files or credentials with the invoking user's privileges, although there is no evidence the current installer is malicious.
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 execution of remote shell or PowerShell code without requiring explicit approval for local installation or explaining its effects. Although this occurs only when the CLI is missing, it expands a read-oriented Mindbody task into local code execution with the invoking user's privileges.
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