Security audit
Security checks for vulnerabilities and agentic risk
The n8n actions have clear approval controls, but setup runs unverified remote code and omits the CLI’s automatic installation of additional agent skills.
Review the setup before installing. Use a reviewed, pinned CLI release and a narrowly scoped n8n connection, and understand that OOMOL mediates access to your data. Consider setting OO_SKILLS_SYNC_DISABLED=1 for every CLI invocation to disable startup skill synchronization, as documented in the [command reference](https://github.com/oomol-lab/oo-cli/blob/main/docs/commands.md). Preserve the required approvals for writes and deletions. The remote installer and deployed connector were not verified.
The supplied command executes an external installer, with no visible n8n interaction or demonstrated connection to implementing the declared n8n functionality. This is a materially different operation involving an inconsistent resource, not an established supporting implementation detail. The downloaded script's contents and any further effects are not available in the supplied code.
The supplied chunk only initiates an oo login and contains no identifiable n8n integration or data operations. Authentication could be a supporting implementation detail, but nothing supplied connects this command to n8n. As presented, its primary behavior differs from the declared purpose.
The setup command pipes a mutable remote script directly into Bash without version pinning, integrity verification, or review; the PowerShell alternative has the same weakness. Although conditional installation is a legitimate dependency step, compromise of the distribution endpoint or release pipeline could execute attacker-controlled code with the agent process's privileges, exposing local data and credentials.
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