Security audit
Security checks for vulnerabilities and agentic risk
The MX functions have clear approval safeguards, but missing software can trigger an unverified remote installer without a separate approval step.
Review and approve CLI installation separately before enabling automatic setup. Inspect a fixed installer release and check whether it adds other agent skills. OOMOL mediates your MX connection; use narrowly scoped access and retain the documented write and deletion approvals. The external installers and CLI runtime were not verified.
The supplied command installs software from an unrelated service and contains no visible MX operations or evidence that this installer supports MX functionality. Remote installer execution is not disclosed by the description. The downloaded script is not supplied, so its further behavior cannot be assessed.
The command pipes a mutable network response directly into Bash without checking a pinned version, trusted digest, or signature; the PowerShell alternative has the same issue. Compromise of the installer distribution path could execute arbitrary code with the agent's local permissions, exposing accessible files and credentials; HTTPS and an apparently relevant vendor domain do not establish artifact integrity.
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 missing-command fallback directs the agent to install software without first explaining the system changes or obtaining installation approval. An ordinary MX request can therefore expand into local code execution and persistent environment changes, although the conditional fallback and declared Bash(oo *) restriction reduce exposure if that restriction is enforced.
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