Security audit
Security checks for vulnerabilities and agentic risk
The Moosend workflow has clear safeguards, but its setup instructions allow remote code execution and broader agent changes without clear user approval.
Review and approve CLI installation separately before allowing the agent to perform it. Prefer a pinned, verified release, and review the CLI's automatic skill installation behavior; the vendor documents OO_SKILLS_SYNC_DISABLED as an opt-out in its [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Understand that OOMOL intermediates subscriber requests and manages the connected Moosend credentials. The remote installer and hosted implementation were not verified; the bundled artifact shows no evidence of malicious intent.
The supplied code performs remote software installation rather than any visible Moosend operation. Although dependency installation can be a supporting implementation detail, this chunk provides no evidence that the Oomol installer supports the declared Moosend purpose. The downloaded script's contents and further effects cannot be determined from the supplied code.
The curl-to-bash command executes mutable remote content with the invoking user's permissions, without a pinned version or integrity verification. Compromise of the installation host or distribution pipeline could therefore yield local code execution and access to files or credentials; HTTPS and the legitimate dependency relationship do not eliminate that 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 missing-CLI fallback directs installation through immediate execution of downloaded scripts, without requiring informed user approval for executing remote code and modifying the local system. Restricting this to a missing dependency reduces exposure, but it does not establish consent or verify the downloaded code.
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