Security audit
Security checks for vulnerabilities and agentic risk
Browser Use actions require approval, but the setup path executes unverified remote code and can introduce additional agent skills without explaining those changes.
Review and install the CLI separately before using this skill. Decide whether to allow its additional agent skills; upstream documents OO_SKILLS_SYNC_DISABLED=1 to disable startup synchronization. OOMOL mediates the connected account and task requests, so use an appropriately scoped account and review each task payload. The remote installer contents and resulting release were not verified.
The supplied chunk installs software from a different service and contains no Browser Use operations or evidence that this installation supports the declared service. Remote installer execution is a materially different capability from the described browser-data tasks. The downloaded script's contents are not supplied, so its further behavior cannot be determined.
The supplied code only invokes a CLI login command. It contains no Browser Use operations or evidence connecting this authentication step to browser-use.com. Although authentication can be a supporting implementation detail, the supplied chunk does not establish that relationship and instead presents a materially different function.
The setup command pipes a mutable remote script directly into Bash without pinning or independently verifying the downloaded content; the PowerShell alternative uses the same download-and-execute pattern. Compromise of the distribution endpoint or release process could execute attacker-controlled code with the invoking user's privileges, exposing local files and credentials. Limiting this behavior to missing-CLI errors reduces exposure but does not remove the supply-chain 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
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