Security audit
Security checks for vulnerabilities and agentic risk
The Mux workflow has sensible approval controls, but setup directs your agent to execute an unverified remote installer without separate approval.
Review and install the CLI separately before enabling this skill, using a verified release and checking its automatic skill synchronization settings. Confirm the intended Mux account and every write or deletion. The bundled text shows no malicious intent, but the remote installers could not be inspected and their effects remain uncertain.
The supplied code executes an Oomol-hosted installer rather than performing any visible Mux operation. Although dependency installation can be a supporting implementation detail, nothing supplied establishes this installer's role in the declared Mux functionality. The remote script's contents and any further effects are not available for assessment.
The command pipes a mutable HTTPS response directly into Bash without verifying a pinned version, signature, or trusted digest; the PowerShell alternative has the same execution pattern. A compromised distribution endpoint or installer could execute arbitrary code with the agent's local permissions, although the skill provides no evidence that the endpoint is currently 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
When the CLI is missing, the fallback directs the agent to execute downloaded installation code without explaining its host-level effects or obtaining explicit installation approval. This expands a Mux data task into local software installation, potentially exposing files, credentials, and configuration accessible to the executing account; the conditional trigger and declared oo-only tool restriction reduce reachability but do not make the installation instructions safe.
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