Security audit
Security checks for vulnerabilities and agentic risk
The BrowserStack workflow is clearly scoped, but setup directs the agent to execute downloaded software without requiring approval or verifying it first.
Review the setup before installing. Prefer a pinned, independently verified CLI installation and require approval before the agent installs software. Check which additional agent skills the CLI installs. OOMOL will mediate your connected BrowserStack access; the remote installer contents and full local effects remain unverified.
The supplied command accesses Oomol infrastructure and executes its installer rather than performing BrowserStack operations. Nothing in the supplied chunk establishes this installer as a supporting dependency for BrowserStack, so its behavior materially differs from the declared purpose. The downloaded script's further actions cannot be determined from this chunk.
Piping an HTTPS response directly into bash executes mutable remote code without a pinned version, independent integrity verification, or review. Compromise of the installer hosting or distribution pipeline could yield arbitrary code execution with the invoking user's permissions; the PowerShell fallback has the same issue, although execution is conditional on missing tooling.
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 instructs the agent to install software after a missing-command error without requiring approval for local system changes. Although limited to first-time setup, a BrowserStack request does not itself authorize installing software or executing an installer with the agent's local permissions.
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