Security audit
Security checks for vulnerabilities and agentic risk
Moorcheh operations have clear safeguards, but missing-CLI setup directs the agent to execute downloaded code without separate installation approval.
Review setup before enabling this skill. Install the CLI through a separately approved process with verified provenance, and require approval before executing downloaded installers. Expect Moorcheh requests to pass through OOMOL, and retain the documented confirmation requirements for writes and deletions. The external installer and backend were not verified; no malicious behavior was established in the bundled artifact.
The supplied command performs remote installer execution, not Moorcheh data operations. Nothing in the supplied content establishes that this installer is a supporting dependency for Moorcheh. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
The only supplied behavior is oo auth login. Nothing in the chunk connects that CLI or its authentication target to Moorcheh. Authentication could be a supporting implementation detail if such a connection were established, but the supplied content instead presents a materially different, login-only purpose.
The curl-to-bash pipeline immediately executes whatever script the remote endpoint currently serves, without version pinning or independent integrity verification. Compromise of the distribution endpoint or release infrastructure could yield arbitrary code execution with the invoking user's privileges, potentially exposing local files and credentials; HTTPS alone does not prevent that scenario.
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 fallback setup directs execution of downloaded shell or PowerShell code without an explicit installation approval step or explanation of host changes. Although installation is relevant and conditional, a missing CLI can expand a routine data request into host-level code execution; the declared Bash tool restriction may limit execution in some environments but is not a substitute for safe setup guidance.
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