Security audit
Security checks for vulnerabilities and agentic risk
The Mautic actions have clear safeguards, but setup can run unverified downloaded software whose documented behavior includes broader changes to agent skills.
Review and install the CLI separately before allowing this skill to run. Check its automatic skill synchronization settings and approve any broader agent changes. Expect Mautic requests and contact data to pass through OOMOL, and retain confirmation for writes and deletions. The complete bundled artifact was reviewed, but remote installers and backend behavior remain unverified; no malicious behavior was established.
The visible behavior is remote installer execution, not Mautic data management. Although installing dependencies can be a supporting implementation detail, the supplied chunk provides no evidence that this installer supports Mautic. The downloaded script's contents are unavailable, so its further behavior cannot be determined.
Piping a remotely fetched script directly into bash executes mutable network content without inspection, version pinning, or independent integrity verification; the PowerShell alternative has the same weakness. If the distribution endpoint or release pipeline is compromised, the installer can run arbitrary commands with the agent's local privileges, potentially accessing files and credentials. The legitimate dependency relationship and conditional setup narrow exposure but do not remove 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 install software by executing third-party scripts without first obtaining explicit approval for local code execution and system changes. Limiting setup to a missing CLI reduces exposure, but the confirmation rules for Mautic writes do not cover installation; a user requesting a Mautic read has not necessarily authorized changes to the local environment.
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