Security audit
Security checks for vulnerabilities and agentic risk
The Brevo operations have clear approval safeguards, but setup can execute unverified remote code and introduce broader changes to your agent environment.
Review and approve CLI installation separately, using an inspected, verified release. Consider whether OOMOL should handle your Brevo connection and contact data. Upstream documents OO_SKILLS_SYNC_DISABLED as a control against automatic skill synchronization. The downloaded installer and hosted connector implementation remain unverified. [CLI controls](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md)
The supplied code's sole visible action is remote installer execution, which is materially different from the declared Brevo functionality. Nothing in the chunk establishes this installer as a supporting dependency for Brevo operations. The downloaded script's contents and further effects cannot be determined from the supplied code.
Piping a live remote script directly into Bash executes whatever the installation endpoint supplies with the invoking user's permissions, without a pinned version or independent integrity verification. Compromise of the vendor endpoint or distribution pipeline could therefore compromise the local host; HTTPS protects transport but does not establish script trustworthiness. The PowerShell installation alternative has the same underlying issue.
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-command fallback directs installation without requiring user approval or explaining that downloaded code will execute locally and may modify the system. Restricting installation to first-time setup reduces exposure, but authorization to operate Brevo does not necessarily authorize installing software on the host.
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