Security audit
Security checks for vulnerabilities and agentic risk
Customer.io changes require your approval, but automatic setup runs unpinned remote installers and under-discloses possible changes to other agent skills.
Before enabling this skill, install a pinned, verified CLI yourself and review or disable its automatic synchronization of other agent skills. Check OOMOL's handling of customer data and connected-account permissions, and retain the explicit approvals for writes and deletions. The remote installers and connector implementation remain unverified; no malicious behavior was established.
The supplied chunk performs remote script execution rather than any visible Customer.io operation. Installing dependencies can be a supporting implementation detail, but nothing provided establishes that this Oomol installer supports the declared Customer.io functionality. The assessment is limited to the visible download-and-execute behavior; the remote script's further actions are unknown.
Piping a mutable remote installer directly into bash executes its contents without prior inspection or cryptographic verification of a specific release. HTTPS protects transport but does not prevent a compromised distribution endpoint from supplying malicious code; the conditional setup path limits exposure but still permits execution with the user's local privileges.
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 code without explicit installation approval or an integrity-verification step. A legitimate dependency requirement explains the behavior but does not authorize arbitrary local code execution; a compromised installer could access files and credentials with the invoking user's privileges.
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