Security audit
Security checks for vulnerabilities and agentic risk
The Skyvern actions have clear approval rules, but automatic setup can execute unreviewed remote code and introduce broader persistent agent changes.
Review and approve CLI installation separately, including whether it installs or synchronizes other agent skills. Use a reviewed, pinned CLI version and confirm browser-task payloads and cancellations. OOMOL intermediates your Skyvern account access. The remote installer and live connector implementation were not bundled, so their complete behavior remains unverified.
The supplied code performs remote installer execution rather than Skyvern data operations. Nothing in the chunk establishes that this installer is a supporting dependency for Skyvern. The downloaded script's contents are not supplied, so its additional behavior cannot be assessed.
Piping a mutable remote script directly into Bash executes its contents without verifying a pinned artifact or reviewing the code first. HTTPS protects transport but does not prevent a compromised installer host or publishing pipeline from delivering code that could access local files and credentials; the legitimate dependency context and conditional fallback reduce exposure but do not eliminate this risk.
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 remotely downloaded shell or PowerShell scripts without requiring explicit installation approval or explaining local system changes. Although limited to a missing-CLI error, this turns a Skyvern request into potential local code execution with the invoking user's privileges.
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