Security audit
Security checks for vulnerabilities and agentic risk
Voiceflow actions have clear safeguards, but setup tells the agent to execute a remote installer without separate approval or integrity checks.
Review and approve CLI installation separately before allowing setup to run; prefer a verified fixed release. Understand that Voiceflow requests pass through OOMOL, and retain the required confirmations for writes. The installation workflow warrants review, but the inspected artifact does not establish malicious behavior.
The supplied code runs an Oomol installation script rather than performing Voiceflow operations. Nothing in the supplied chunk establishes that this installation supports Voiceflow, so it represents an undeclared capability involving a different service. The downloaded script's contents and further effects are not available for assessment.
The command pipes a mutable remote script directly into Bash without pinning a release or verifying its integrity. If the installer host or publishing pipeline is compromised, the script could execute arbitrary commands with the invoking user's permissions, including accessing local credentials; HTTPS alone does not protect against a compromised publisher.
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 setup directs execution of downloaded shell or PowerShell code without first explaining the local changes or obtaining explicit installation approval. Although installing a required connector is legitimate, a missing CLI should not implicitly authorize executing remote code with the agent's local privileges; the oo-only tool allowance may constrain execution but does not make these instructions safe.
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