Security audit
Security checks for vulnerabilities and agentic risk
Review is needed because setup can execute an unverified remote installer without separate approval or explaining its broader changes to your agent.
Review and approve CLI installation separately. Check which additional agent skills it installs before connecting MailBluster. The [CLI documentation](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md) describes OO_SKILLS_SYNC_DISABLED for preventing startup skill synchronization. MailBluster writes and deletion already require approval. No malicious behavior was established, but the external installer remains uninspected.
The supplied code performs remote installer execution rather than any visible MailBluster operation. Nothing in the provided content establishes this installer as a supporting dependency for MailBluster functionality. The downloaded script's contents are not supplied, so its further behavior cannot be assessed.
The command pipes a mutable remote response directly into Bash without verifying a pinned artifact or signature; the PowerShell alternative has the same trust problem. Compromise of the distribution endpoint or release pipeline could therefore execute attacker-controlled code with the user's privileges, although HTTPS and the conditional setup path reduce some exposure.
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 setup instructions direct installation without requiring approval for executing downloaded code or explaining local system changes. Installation executes with the invoking user's privileges and may modify files or access sensitive data; limiting setup to missing-CLI errors reduces exposure but does not establish user consent.
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