Security audit
Security checks for vulnerabilities and agentic risk
The MOCO reading functions are clearly scoped, but setup can trigger execution of an unverified remote installer without a clear approval step.
Review and install a fixed CLI release separately before enabling this skill, and require approval for installation or changes to other agent skills. OOMOL mediates access to your MOCO account, so review the permissions you connect. The concrete concern is setup control; the artifact does not establish malicious behavior.
The supplied code performs a remote installation rather than the declared MOCO data-access function. Nothing in the chunk establishes that the Oomol installer is a supporting dependency for MOCO access. The remote script's contents are unavailable, so its further actions cannot be determined.
Piping a remotely fetched installer directly into Bash executes its current contents with the agent process's privileges, without a pinned version or independent integrity verification. Compromise of the installer distribution could therefore expose local data or permit arbitrary system changes; the Windows download-and-execute example has the same issue. HTTPS and the setup-only trigger reduce some exposure but do not verify the publisher's delivered code.
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 prompts installation through immediate execution of a downloaded script, without requiring user approval or explaining that installation can modify the local environment. The missing-command condition limits exposure, but an ordinary read-only MOCO request could still lead to system-changing setup if those commands are permitted.
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