Security audit
Security checks for vulnerabilities and agentic risk
The Intercom workflow has clear safeguards, but setup can automatically execute an unverified remote installer.
Review and verify the CLI installer before allowing setup to execute it. OOMOL mediates access to your Intercom account and customer data; check the permissions you grant. The skill explicitly requires approval for account changes and destructive actions. The external installer and hosted connector were not fully assessed.
The visible behavior installs software from Oomol rather than interacting with Intercom. Dependency installation can be a supporting implementation detail, but the supplied chunk provides no evidence that this installer supports the declared purpose. The downloaded script's contents and further effects are not available for assessment.
The setup instructions pipe a mutable remote script directly into bash without verifying its integrity or reviewing its contents; the PowerShell alternative has the same issue. A compromised installer endpoint or release pipeline could execute arbitrary code with the agent's local privileges and access local secrets or files. Restricting installation to a missing-CLI error reduces exposure but does not establish trust in the downloaded code.
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
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