Security audit
Security checks for vulnerabilities and agentic risk
The Omnisend workflow is clearly scoped, but its fallback setup executes unverified remote code without a separate approval step.
Review and approve CLI installation separately, using a verified release where possible. Check its automatic skill installation and synchronization settings before running it. Connecting Omnisend entrusts OOMOL with account access and contact operations; keep permissions narrow and retain the documented confirmations. Only the bundled instructions were fully inspectable; the remote installers and hosted connector implementation remain unverified.
The supplied code performs no visible Omnisend operations. Its sole action is to fetch and execute an Oomol installation script, which is not described by the declared purpose or shown to be a supporting dependency. The remote script's contents are unavailable, so its additional behavior cannot be assessed.
Piping a live HTTPS response directly into bash executes mutable remote code with the agent process's local privileges, without an independent integrity check or review. Although the URL is consistent with the documented CLI provider and execution is conditional on missing software, compromise of the distribution endpoint could expose local credentials or permit arbitrary system changes; the PowerShell installation example 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
When the CLI is missing, the setup instructions direct installation without requiring approval for executing downloaded code or modifying the local environment. Limiting setup to an actual missing-command error reduces exposure, but permission to perform Omnisend operations does not necessarily authorize software installation; the confirmation requirements elsewhere cover Omnisend data changes, not local setup.
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