Security audit
Security checks for vulnerabilities and agentic risk
Review the setup before installing: it directs automatic execution of remote code and omits the CLI’s documented changes to other agents’ skills.
Approve CLI installation separately and verify a fixed release before executing it. The publisher documents OO_SKILLS_SYNC_DISABLED=1 to prevent startup skill synchronization; consider setting it before running the CLI. Use only the intended Discourse account and confirm public post contents. The remote installers’ complete effects remain unverified.
The supplied code installs a third-party CLI rather than performing Discourse operations. Nothing in the chunk establishes this installation as a supporting dependency for Discourse. The remote script's contents are not supplied, so its additional effects cannot be assessed.
Piping a remotely fetched script directly into Bash executes mutable external code without prior review or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the installer delivery path could execute attacker-controlled code with the agent's local permissions, although the missing-CLI condition and any enforced tool restrictions limit when this path is reachable.
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 instructs the agent to install software without obtaining approval for local code execution and system changes, which exceeds an ordinary Discourse data request. The explicit confirmation requirements cover Discourse writes but not installation; strict enforcement of the declared Bash(oo *) tool restriction would reduce exposure by blocking the shown installation commands.
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