Security audit
Security checks for vulnerabilities and agentic risk
The Emailable integration is coherent, but its setup permits unchecked remote code execution and does not explain broader changes its CLI can make to agent skills.
Review and approve a verified, pinned CLI installation before allowing setup. Consider setting OO_SKILLS_SYNC_DISABLED=1 before CLI use to prevent changes to other agent skills. Only verify addresses you are authorized to send through OOMOL to Emailable, and check applicable credit costs. The packaged instructions were fully inspected; remote installer contents and the installed CLI version remain unverified.
The supplied command performs remote script execution for an Oomol installer, with no visible Emailable API interaction or demonstrated connection to the declared purpose. This is an undeclared installation capability, not an established supporting implementation detail. The downloaded script's contents and downstream effects cannot be determined from this snippet.
The installation command streams a mutable remote script directly into a shell without a pinned version or independent integrity verification; the PowerShell alternative has the same weakness. If the distribution endpoint or release infrastructure is compromised, installation can execute attacker-controlled code with the invoking user's privileges, potentially exposing local files and credentials. The missing-CLI condition limits when this occurs but does not make the execution safe.
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 untagged verify_email action falls under the instruction that untagged actions are safe to run directly. Although the skill identifies the OOMOL/Emailable integration, it never warns that verification transmits the supplied email addresses through OOMOL to Emailable; confirmation for state-changing actions does not cover this privacy impact.
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