Security audit
Security checks for vulnerabilities and agentic risk
Mailercloud actions have approval safeguards, but setup can execute unverified remote code and introduce undisclosed changes to other agent skills.
Review and approve a verified CLI installation before use, and review or disable its automatic installation and synchronization of other agent skills. OOMOL will handle your Mailercloud connection and requests. Keep account permissions limited and retain the stated approval checks for changes and deletions. The remote installers and exact runtime release remain unverified.
The supplied chunk performs remote software installation rather than Mailercloud data operations. Although installation can be a supporting implementation detail, nothing in the supplied content connects this Oomol installer to the declared Mailercloud functionality. The downloaded script's contents are not provided, so its further behavior cannot be determined.
Piping the HTTPS installer directly into bash executes mutable remote content without version pinning, integrity verification, or an opportunity for review. Compromise of the distribution endpoint could therefore result in arbitrary code execution with the invoking process's permissions; the legitimate CLI dependency explains the purpose but does not establish the downloaded script's integrity.
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 setup instructions direct execution of downloaded shell or PowerShell scripts without explaining their local effects or requiring explicit installation approval. Such scripts execute with the invoking process's permissions and could modify files or access locally available secrets; conditional execution only when the CLI is missing reduces exposure but does not remove this risk.
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