Security audit
Security checks for vulnerabilities and agentic risk
The GitHub workflow includes approval safeguards, but its setup fallback runs downloaded code without clearly requiring permission for local changes.
Review and install a verified CLI release yourself, and require approval before any setup changes. Check its automatic skill synchronization settings and grant only the GitHub permissions you need. GitHub changes already require confirmation. The full bundled skill was inspected, but downloaded installer contents and hosted-service behavior remain unverified; no malicious behavior was established.
The supplied command executes an installer from cli.oomol.com rather than performing a GitHub operation. Nothing in the supplied chunk establishes this installer as a supporting dependency for GitHub functionality. The remote script's contents and any further effects cannot be determined from this chunk.
Piping a remotely fetched script directly into Bash executes mutable network content with the agent process's local privileges, without prior inspection or integrity verification. Compromise of the installer distribution could expose local files and credentials or modify the host; the PowerShell example has the same weakness, although neither example proves malicious intent.
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 an installer without explicitly obtaining approval for local code execution or system changes. Although limited to first-time setup, it crosses from GitHub operations into modifying the host, and the GitHub action confirmation rules do not clearly cover this step.
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