Security audit
Security checks for vulnerabilities and agentic risk
The Discord actions have clear approval safeguards, but setup can execute an unverified remote installer without separate user approval.
Review the CLI installation separately before allowing setup, and use a version whose source and integrity you can verify. OOMOL mediates your Discord account access. Also review its documented automatic skill installation and synchronization; the current [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) documents OO_SKILLS_SYNC_DISABLED to disable startup synchronization. The remote installer and hosted connector implementation were not verified, so their exact runtime effects remain uncertain.
The supplied command executes a remote installer rather than performing Discord operations. Dependency installation can be a supporting implementation detail, but the supplied chunk provides no evidence that this installer supports Discord functionality. The remote script's contents and any additional effects cannot be determined from this snippet.
Piping the HTTPS response directly into bash executes mutable remote content without a pinned version or independently verified integrity; the PowerShell alternative has the same underlying risk. Compromise of the distribution endpoint could result in arbitrary code execution, including theft of accessible credentials or modification of local files, although the supplied skill provides no evidence that the endpoint is 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
The setup fallback directs installation through downloaded scripts without explaining that this executes remote code with the local user's privileges or requiring explicit installation approval. Restricting setup to a missing-CLI error reduces exposure, but a routine Discord request can still lead to consequential local execution beyond the requested service operation.
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