Security audit
Security checks for vulnerabilities and agentic risk
The email workflow is well scoped, but its automatic setup can run unverified downloaded code without separate user approval.
Review and approve CLI installation separately, preferably using a verified release. Consider disabling its automatic agent-skill synchronization. Connecting ProxiedMail lets OOMOL process email requests and manage forwarding bindings. The bundled instructions were fully inspected, but the remote installer and hosted connector implementation were not verified.
The declared purpose is ProxiedMail data access and management, but the supplied command executes an Oomol installation script. Nothing in the supplied chunk establishes that this installation supports ProxiedMail, so it represents an undeclared capability and an inconsistent resource. The remote script's contents are not provided, so its further behavior cannot be determined.
Piping an HTTPS response directly into bash executes mutable remote code without inspecting or independently verifying it. HTTPS protects transport but not against compromise of the installer host or publishing pipeline, which could result in credential theft or local code execution; the PowerShell alternative has the same underlying 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 explicitly obtaining approval for local system changes or verifying the downloaded artifact. Although this is a legitimate dependency setup step and only runs after a missing-command error, a compromised installer could execute arbitrary commands with the invoking user'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