Security audit
Security checks for vulnerabilities and agentic risk
The mailbox controls are sensible, but setup can execute an unverified remote installer without first asking for approval.
Review before installing. You must trust OOMOL with the connected mailbox. Install a reviewed, verified CLI release yourself, review its automatic bundled-skill synchronization, and retain approval requirements for sending, modifying, or deleting email. Remote installer contents and hosted connector behavior remain unverified; the artifacts do not establish malicious intent.
The only supplied command executes an external installation script; it does not connect to or manage an IMAP mailbox. Dependency installation could be a supporting implementation detail, but the supplied chunk establishes no connection between this installer and the declared mailbox functionality. The downloaded script's contents and any further effects are not available for assessment.
Piping a mutable remote script directly into Bash executes its contents without an independent authenticity check or review. HTTPS protects transport but does not prevent a compromised publisher or distribution endpoint from serving malicious code, which would run with the agent's local privileges; the PowerShell example has the same 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
The fallback directs the agent to execute remotely supplied installation code without first obtaining approval for local code execution and system changes. Although triggered only when the CLI is missing, this expands a mailbox request into host-level software installation; malicious or compromised installer content could access local files and credentials with the agent's privileges.
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