Security audit
Security checks for vulnerabilities and agentic risk
The mail workflow is clearly scoped, but setup can execute an unverified downloaded installer without separate user approval.
Review the setup before installing. Prefer a verified, fixed CLI release installed under your control, and require approval before any automatic installation. Review its cross-agent skill installation behavior and grant only the AgentMail access you need. Mail changes and deletions already require confirmation. The remote installer contents remain unverified; no malicious behavior was established.
The supplied code performs remote installer execution rather than AgentMail data operations. Nothing in the chunk establishes that this installer is a supporting dependency for AgentMail. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
The command immediately executes a mutable remote script without a pinned version or independently verified integrity; the PowerShell alternative has the same property. Compromise of the installer distribution path could execute arbitrary code with the invoking user's privileges, potentially exposing local files and credentials. The domain is relevant to the documented CLI dependency and HTTPS helps protect transport, but neither establishes the integrity of the delivered code.
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 install software on the local system without first explaining the changes or obtaining explicit installation approval. The missing-command prerequisite limits when this happens, but the confirmation rules for AgentMail writes do not cover local software 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