Agent skill · AI & Agents

agent-browser

Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill agent-browser-clawdbot --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Path: skills/agent/agent-browser-clawdbot/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Agent Browser Skill Fast browser automation using accessibility tree snapshots with refs for deterministic element selection. ## Why Use This Over Built-in Browser Tool **Use agent-browser when:** - Automating multi-step workflows - Need deterministic element selection - Performance is critical - Working with complex SPAs - Need session isolation **Use built-in browser tool when:** - Need screenshots/PDFs for analysis - Visual inspection required - Browser extension integration needed ## Core Workflow ```bash # 1. Navigate and snapshot agent-browser open https://example.com agent-browser snapshot -i --json # 2. Parse refs from JSON, then interact agent-browser click @e2 agent-browser fill @e3 "text" # 3. Re-snapshot after page changes agent-browser snapshot -i --json ``` ## Key Commands ### Navigation ```bash agent-browser open <url> agent-browser back | forward | reload | close ``` ### Snapshot (Always use -i --json) ```bash agent-browser snapshot -i --json # Interactive elements, JSON output agent-browser snapshot -i -c -d 5 --json # + compact, depth limit agent-browser snapshot -s "#main" -i # Scope to selector ``` ### Interactions (Ref-based) ```bash agent-browser click @e2 a

What's inside
Steps it walks through
  1. Why Use This Over Built-in Browser Tool
  2. Core Workflow
  3. Key Commands
  4. Navigation
  5. Snapshot (Always use -i --json)
  6. Interactions (Ref-based)
  7. Get Information
  8. Check State
  9. Wait
  10. Sessions (Isolated Browsers)
  11. State Persistence
  12. Screenshots & PDFs
  13. Network Control
  14. Cookies & Storage
Ships with 1 file
  • metadata.json
Commands it runs
agent-browser open https://example.com
agent-browser snapshot -i --json
agent-browser click @e2
agent-browser fill @e3 "text"
agent-browser open <url>
agent-browser back | forward | reload | close
agent-browser snapshot -i --json          # Interactive elements, JSON output
agent-browser snapshot -i -c -d 5 --json  # + compact, depth limit
agent-browser snapshot -s "#main" -i      # Scope to selector
agent-browser type @e3 "text"
More from claude-skill-registry
All skills →
descriptive-statisticsSummarizing and visualizing data through measures of center, spread, shape, and position. Covers…Data & Analyticsperplexity-researcher-reasoning-proHighest level of research and reasoning capabilities for complex decision-making with significant…OtherretroBrutally honest engineering retrospective. Analyzes git history for what actually happened — not…Data & AnalyticsanalyzeUniversal multi-perspective analyzer for any topic, file, idea, or decision. Extract key points…Otherarize-prompt-optimizationINVOKE THIS SKILL when optimizing, improving, or debugging LLM prompts using production trace data…Data & Analyticscellxgene-contextGuide for integrating CellxGene Census single-cell data with ENCODE bulk experiments. Use when…Data & Analytics
About this skill
What does the agent-browser skill do?

Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill agent-browser-clawdbot --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.