Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Openclaw Skill Browser Use
v1.0.0Autonomous browser automation for AI agents. Two tools: agent-browser (CLI Playwright for step-by-step control) and browser-use (Python autonomous agent that...
⭐ 0· 41·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The stated purpose (CLI Playwright control + autonomous Python agent) matches the provided files and commands. Requiring node/npm/python3/chromium/xvfb is coherent for browser automation. However the skill does not declare required environment variables in registry metadata even though the scripts expect OPENAI_API_KEY or ANTHROPIC_API_KEY (and will auto-detect them from /root/.openclaw/openclaw.json). That discrepancy (no declared env but runtime use of credentials) is a notable mismatch.
Instruction Scope
SKILL.md and the included scripts direct the agent to run arbitrary browser actions (open, click, eval JS) which is expected. The installer and wrappers (scripts/install.sh and scripts/browser-use-agent.sh) read /root/.openclaw/openclaw.json to extract API keys if env vars are not set — this is reading a central agent config file outside the skill's declared scope. The wrapper also prints/executes a temporary Python script using those keys. Accessing a root OpenClaw config for secrets is scope creep and potentially surprising.
Install Mechanism
There is no registry install spec, but an included scripts/install.sh performs apt-get installs, npm -g install agent-browser, pip installs of browser-use and langchain-* packages, and playwright browser installs. These are standard package sources (apt, npm, PyPI, Playwright) rather than arbitrary downloads, but the installer creates system-wide artifacts (/opt/browser-use, /usr/local/bin/browser-use-agent) and may require sudo. Global npm/pip installs and Playwright downloads should be reviewed before running.
Credentials
The skill will use LLM provider keys (OPENAI_API_KEY or ANTHROPIC_API_KEY) which are reasonable for an autonomous browsing agent, but the registry lists no required env vars. More importantly, both the wrapper and browser-use-agent.sh will attempt to pull keys from /root/.openclaw/openclaw.json if env vars are unset, which accesses central credentials. Reading that file can expose API keys stored by the platform — this is a high-sensitivity access that the skill did not declare.
Persistence & Privilege
Although always:false and model invocation is allowed (normal), the installer writes persistent, system-wide files: a venv in /opt/browser-use and a wrapper in /usr/local/bin/browser-use-agent. Combined with the auto-detection of keys from /root/.openclaw/openclaw.json, this persistent presence increases blast radius if keys are accessible. The installer also runs privileged package installs (apt-get) and global npm installs — running it as root or with sudo should be done cautiously.
What to consider before installing
What to consider before installing or running this skill:
- The skill's functionality (headless browser automation + autonomous agent) is consistent with the files provided, but the scripts will try to read OpenClaw's central config (/root/.openclaw/openclaw.json) to auto-fill OPENAI_API_KEY or ANTHROPIC_API_KEY if you haven't exported them. That file can contain sensitive API keys for other services — decide whether you want this skill to access them.
- The included installer performs system-wide changes: apt-get package installs, npm -g agent-browser, pip installs, Playwright browser downloads, creates /opt/browser-use and /usr/local/bin/browser-use-agent. Only run the installer on systems you control and understand; prefer running in a disposable VM/container or sandbox.
- If you want to avoid the skill auto-reading platform credentials, set OPENAI_API_KEY or ANTHROPIC_API_KEY in the environment explicitly before running, or inspect and modify the wrapper/browser-use-agent.sh to remove the auto-detection lines that read /root/.openclaw/openclaw.json.
- Review the npm package agent-browser and the PyPI package browser-use (and their dependencies) before global installation: npm packages can run postinstall scripts. If possible, install locally or pin versions.
- Do not run the installer as root on a production host unless you accept the system-wide changes. Consider running the CLI-only agent-browser interactions without running the installer (if agent-browser is already present) or using a container.
- If you want to proceed, audit scripts/install.sh and scripts/browser-use-agent.sh line-by-line (they are included) and confirm you accept creation of /opt and /usr/local artifacts and the reading of /root/.openclaw/openclaw.json.Like a lobster shell, security has layers — review code before you run it.
latestvk97c8hqbjnq6gcwc9dpnx93jw183s7tg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
🌐 Clawdis
Binsnode, npm, python3