Security audit
Security checks for vulnerabilities and agentic risk
The Nango integration is coherent, but automatic software installation and insufficient safeguards around credential-returning reads warrant review.
Review and install the CLI separately before allowing this workflow, including its effects on other installed agent skills. Give OOMOL a narrowly scoped Nango key, exclude credential-reading permissions unless needed, and treat returned connection details as potentially secret. Keep the required approvals for writes and deletions. Remote installer and hosted backend behavior were not verified; no malicious payload was established.
The supplied command installs software from an Oomol domain and contains no Nango operations or evidence that this installation supports Nango. Its visible behavior therefore materially differs from the declared purpose. The downloaded script is not supplied, so its additional effects cannot be determined.
The supplied chunk only initiates an oo login and contains no Nango-specific operations or configuration. Authentication could support a Nango integration, but no connection between this CLI and Nango is established in the supplied material.
The command pipes a remotely fetched, mutable script directly into Bash without pinning or independent integrity verification; the PowerShell alternative follows the same pattern. If the distribution endpoint or release process is compromised, the installer can execute arbitrary code with the invoking user's permissions, potentially exposing local credentials and files. HTTPS and the conditional setup path reduce some exposure but do not establish the script's integrity.
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 missing-CLI fallback instructs the agent to execute a downloaded installer without first obtaining approval for local software installation or explaining its system effects. This expands an ordinary Nango task into local code execution; making installation conditional reduces exposure but does not establish user consent.
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