Security audit
Security checks for vulnerabilities and agentic risk
Mingdao changes require your approval, but setup directs the agent to run downloaded installers without a separate installation approval step.
Review and approve CLI installation separately, including whether it will add or update skills in your other agents. Prefer a verified release, restrict the connected Mingdao account's permissions, and retain confirmations for every change. The bundled instructions show no malicious intent, but the external installer and connector behavior remain unverified.
The supplied chunk performs remote software installation rather than the declared Mingdao data operations. Installation could be a supporting implementation detail, but the provided code establishes no connection between this installer and Mingdao functionality. The downloaded script's contents and any further effects cannot be determined from this chunk.
Piping a remotely fetched installer directly into Bash executes whatever content the endpoint currently serves without version pinning, signature verification, or prior review. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from supplying code that accesses local files and credentials; conditional execution only when the CLI is missing reduces exposure, not the potential impact.
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-CLI fallback directs the agent to execute downloaded shell or PowerShell code without explicitly obtaining approval for local installation or explaining its system effects. The confirmation rules cover Mingdao actions, not local setup, allowing a data-operation request to lead to arbitrary code execution with the agent's local privileges if the installer is compromised.
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