Security audit
Security checks for vulnerabilities and agentic risk
The Findymail workflow fits its purpose, but its automatic setup executes unverified downloaded code without a separate approval step.
Review the setup before installing. Install a verified, fixed-version CLI yourself and require approval for installation changes. Review or disable its automatic skill synchronization, and connect Findymail only if you accept OOMOL handling the integration. The remote installers' exact effects remain unverified; no malicious behavior was established.
The supplied command performs remote installer execution, not Findymail data access. Nothing in the code establishes that this installer is a supporting dependency for Findymail, so its installation behavior and unrelated resource access materially differ from the declared purpose. The downloaded script is not supplied, so its further effects cannot be determined.
Piping a remote HTTPS response directly into Bash executes mutable external code without inspecting or verifying the artifact. Compromise of the distribution endpoint or its delivery pipeline could yield arbitrary execution, access to local secrets, and modification of files within the agent's privileges; the legitimate dependency-installation purpose does not eliminate this supply-chain 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 downloaded installation scripts without explicit user approval, integrity verification, or an explanation that installation changes the local system. Although limited to a missing-dependency scenario, a compromised installer could execute arbitrary commands with the agent process's privileges; this overlaps with SC2 rather than representing a separate exploit.
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