Security audit
Security checks for vulnerabilities and agentic risk
The Mezmo queries are appropriately scoped, but setup tells the agent to execute a downloaded installer without a separate approval or verification step.
Review and approve CLI installation separately before allowing automatic setup. Prefer a pinned, verified release. OOMOL is the disclosed intermediary for your connected Mezmo account, so review its access scopes and credential handling. The material concern is the installation boundary; the inspected skill does not establish malicious behavior.
The supplied command performs remote installer execution rather than searching or reading Mezmo data. Nothing in the supplied content establishes that this installer is a necessary supporting implementation detail for Mezmo access. The installer’s contents are not provided, so its further effects cannot be determined.
The command pipes an unpinned remote script directly into Bash, allowing the downloaded content to execute with the invoking user's permissions without review or integrity verification. OOMOL is a relevant dependency rather than an obviously malicious destination, but compromise of its distribution infrastructure could still lead to local credential theft or system modification; the PowerShell example has the same issue.
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
A missing CLI triggers instructions to download and execute installation code without first obtaining approval for local system changes. Although setup is a legitimate prerequisite and is conditional, a read-oriented Mezmo request does not itself authorize arbitrary installer execution; the Bash tool restriction may limit execution but is not a substitute for an explicit setup boundary.
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