← Back to Skills Marketplace
Wayne Agent Browser
by
WechatGpt798
· GitHub ↗
· v1.0.0
· MIT-0
97
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install wayne-agent-browser
Description
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection
Usage Guidance
This skill appears to be a coherent browser-automation CLI, but exercise caution before installing or running it. Things to do before proceeding: 1) Verify the npm package and GitHub repo (https://github.com/vercel-labs/agent-browser) are legitimate and match the version you expect. 2) Prefer installing and running the CLI in an isolated environment (container or VM) because `npm install -g` runs package install scripts and `agent-browser install` downloads Chromium binaries. 3) Avoid loading or saving auth state files (cookies/localStorage) unless you trust the environment and repository; such files can contain sensitive tokens. 4) If you must use it, restrict its filesystem/network permissions and review any downloaded binaries' checksums. 5) If you want lower risk, ask the skill author to declare required binaries and provide an explicit, vetted install spec (trusted release URLs/checksums) so you can audit the installation sources.
Capability Analysis
Type: OpenClaw Skill
Name: wayne-agent-browser
Version: 1.0.0
The skill bundle provides documentation and usage instructions for the 'agent-browser' CLI, a legitimate headless browser automation tool developed by Vercel Labs. The instructions in SKILL.md are purely functional, covering standard automation tasks such as navigation, element interaction, and session management without any evidence of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
The SKILL.md clearly targets a CLI named `agent-browser` and describes installing it with `npm install -g agent-browser`, downloading Chromium, and running many CLI commands. However the registry metadata lists no required binaries or install spec. That mismatch (the skill essentially requires a third-party CLI and npm installs, but the package metadata declares none) is inconsistent and worth noting.
Instruction Scope
The instructions focus on browser automation (navigation, snapshots, refs) which is consistent with the description. However they explicitly instruct saving/loading auth state files (e.g., `state save auth.json` / `state load auth.json`), controlling network routing/mocking, and installing runtime dependencies. Those file I/O and network-control steps can be used to persist or exfiltrate sensitive tokens/cookies or to intercept/modify requests — while legitimate for browser automation, they expand the scope beyond simple read-only scraping and should be considered when granting the tool access.
Install Mechanism
There is no install spec in the registry, but SKILL.md tells users to run `npm install -g agent-browser` and `agent-browser install` (which downloads Chromium). Global npm installs execute package install scripts and will run code from the npm package; the Chromium download will pull external binaries. This is a higher-risk install pattern unless you verify the npm package and download sources are trustworthy (the homepage points to a GitHub repo which helps, but the skill metadata and registry did not declare these installs).
Credentials
The skill declares no required environment variables or credentials (registry shows none). SKILL.md mentions an optional AGENT_BROWSER_SESSION env var for convenience, but no secrets are requested by the skill itself. The main proportionality concern is that the tool reads/writes auth state files (cookies/localStorage), which may contain sensitive credentials even though no env secrets are required.
Persistence & Privilege
The skill is not always-enabled and does not request elevated platform privileges. However the recommended workflows include persisting browser state to disk and loading it later (state save/load), so the tool can create long-lived local files containing session cookies/storage. This is normal for a browser automation tool but increases persistence of sensitive tokens on disk.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install wayne-agent-browser - After installation, invoke the skill by name or use
/wayne-agent-browser - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release of agent-browser skill.
- Headless browser automation CLI specialized for AI agents.
- Deterministic, ref-based element selection using accessibility tree snapshots.
- Supports multi-step workflows, session isolation, and state persistence.
- Comprehensive set of commands for navigation, interaction, state check, network & storage control.
- Includes best practices and usage examples for efficient automation.
Metadata
Frequently Asked Questions
What is Wayne Agent Browser?
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection. It is an AI Agent Skill for Claude Code / OpenClaw, with 97 downloads so far.
How do I install Wayne Agent Browser?
Run "/install wayne-agent-browser" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Wayne Agent Browser free?
Yes, Wayne Agent Browser is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Wayne Agent Browser support?
Wayne Agent Browser is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Wayne Agent Browser?
It is built and maintained by WechatGpt798 (@wechatgpt798); the current version is v1.0.0.
More Skills