Security audit
Security checks for vulnerabilities and agentic risk
The Breeze features match the stated purpose, but setup directs the agent to execute downloaded code without verification or a user approval step.
Review setup before installing. Prefer a separately reviewed, version-pinned CLI and require approval before running its installer. Connect only the intended Breeze account, since personal records are accessed through OOMOL, and review the CLI's additional skill synchronization behavior. Remote installer contents and hosted connector internals remain unverified; the artifacts do not establish malicious intent.
The supplied chunk performs remote script execution rather than searching or reading Breeze data. Although CLI installation could be a supporting implementation detail, nothing supplied establishes that this installer supports Breeze access. The downloaded script's contents and any further effects are not visible, so no specific downstream behavior or malicious intent can be concluded.
Authentication could support a Breeze integration, but the supplied chunk contains no Breeze-specific configuration or data-access behavior establishing that connection. As the entire supplied implementation, the login command has a materially different immediate purpose from the advertised Breeze search-and-read functionality.
The command pipes a mutable remote script directly into Bash without integrity verification or review; the PowerShell alternative has the same trust problem. A compromised distribution endpoint or malicious installer update could execute arbitrary code with the agent's local privileges, potentially accessing files and credentials; HTTPS and the conditional setup trigger do not eliminate that 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
A missing CLI triggers instructions to execute a downloaded installer without a separate user approval step or explanation of local system changes. Although installing a dependency is relevant to Breeze access, a request to read Breeze records does not necessarily authorize executing third-party code on the user's machine.
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