Security audit
Security checks for vulnerabilities and agentic risk
The Y.GY operations are clearly scoped, but setup can execute changing remote code without asking for approval.
Review before installing. Install and verify the CLI separately, require approval for local setup changes, and review its automatic skill-sync behavior. OOMOL mediates access to your connected Y.GY account. The remote installers were unavailable for inspection, so their exact local effects remain unverified.
The visible code installs software from cli.oomol.com rather than performing Y.GY data operations. Nothing supplied establishes that this installer is a supporting dependency for Y.GY. The remote script's contents and any further behavior cannot be determined from this chunk.
The curl-to-bash command executes mutable remote content without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. Compromise of the installer distribution path could execute arbitrary code with the agent process's permissions, exposing accessible files and credentials; HTTPS and the legitimate dependency context do not eliminate that 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
When the CLI is missing, the workflow instructs the agent to install it by immediately executing downloaded code, without requiring informed approval for local system changes. The conditional setup path limits exposure, but the write-action confirmation rules concern Y.GY state and do not clearly protect local installation.
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