Security audit
Security checks for vulnerabilities and agentic risk
The Trigger.dev workflow is clearly scoped, but its setup instructions can run an unverified remote installer without separate user approval.
Review and approve CLI installation separately, preferably using a verified, fixed release. Check its automatic skill-synchronization settings before use. OOMOL is part of the credential and request trust boundary. Preserve the skill's confirmation requirements for changes and cancellations. The remote installer payload was unavailable for inspection.
The supplied command targets an Oomol installation endpoint and executes its response locally. Nothing in the chunk connects that installation to Trigger.dev or implements the declared data operations. This is a material purpose and resource mismatch, not an established supporting implementation detail. The remote script's precise effects cannot be determined from the supplied chunk.
The command pipes a mutable remote script directly into bash without checking its contents, signature, or expected digest; the PowerShell alternative has the same trust problem. Compromise of the installer distribution path could execute arbitrary code with the invoking user's privileges, potentially exposing local credentials and files, although nothing here establishes that the vendor or current installer is malicious.
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 directs the agent to install software without explicitly requiring approval or explaining the installer's potential filesystem, executable, and shell-configuration changes. Although installation is relevant and conditional, a request to operate Trigger.dev does not necessarily authorize running an installer on the user's machine.
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