Security audit
Security checks for vulnerabilities and agentic risk
The mymind operations are clearly controlled, but setup directs the agent to run changeable downloaded code without separate installation approval.
Review and approve CLI installation separately, using a verified release rather than automatically executing the fallback scripts. Check whether automatic installation and synchronization of other agent skills is acceptable; upstream documents OO_SKILLS_SYNC_DISABLED as a control. Your mymind requests pass through OOMOL, and changes or deletions should retain the skill's explicit approval checks. The remote installers and hosted backend were not verified.
The supplied code installs software from an external service rather than performing or exposing the declared mymind operations. Although installing dependencies can be a supporting implementation detail, this chunk provides no evidence that the Oomol installer supports mymind functionality. The downloaded script's contents and any further effects are not visible.
Piping an HTTPS response directly into bash executes mutable remote code without a pinned version or independent integrity verification. Compromise of the installer distribution infrastructure could therefore execute attacker-controlled code with the agent process's permissions; the legitimate dependency relationship and missing-CLI condition reduce exposure but do not eliminate this supply-chain risk.
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 directs the agent to execute downloaded installation scripts without first explaining the local code execution and obtaining installation-specific approval. Although limited to a missing CLI, this moves beyond mymind account operations into changing the host system, potentially with the agent process's access to local files and credentials.
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