agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
npx skills add majiayu000/claude-skill-registry --skill agent-browser-avibebuilder-claude-prime --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Browser Automation with agent-browser Use this skill to drive websites through the `agent-browser` CLI. Keep the main loop tight: inspect the page, act with refs, verify the result, and only pull deeper docs when the task actually needs them. ## Core workflow Prefer `agent-browser` directly for speed. Use `npx agent-browser` only if it is not installed globally. For most tasks, follow this loop: 1. Open the page 2. Wait for the relevant state 3. Snapshot with refs 4. Interact using those refs 5. Re-snapshot after page or DOM changes 6. Verify the outcome 7. Close the session when done ```bash agent-browser open https://example.com/form agent-browser wait --load networkidle agent-browser snapshot -i # Output: @e1 [input type="email"], @e2 [input type="password"], @e3 [button] "Submit" agent-browser fill @e1 "user@example.com" agent-browser fill @e2 "password123" agent-browser click @e3 agent-browser wait --load networkidle agent-browser snapshot -i ``` Chain commands with `&&` only when you do not need to inspect intermediate output. Good: `open && wait && screenshot`. Bad: `snapshot && click` when you still need to read the refs from the snapshot. ## Route fast Read only the refe
- Core workflow
- Route fast
- Golden path commands
- Refs are the default interaction model
- Choose the lightest tool that still proves the result
- Authentication: decide sensitivity first
- Sessions: isolate work on purpose
- Security defaults for AI-driven browsing
- Failure modes to catch early
agent-browser open https://example.com/form agent-browser wait --load networkidle agent-browser snapshot -i agent-browser fill @e1 "user@example.com" agent-browser fill @e2 "password123" agent-browser click @e3 agent-browser open <url> agent-browser click @e1 agent-browser fill @e2 "text" agent-browser select @e3 "option"
What does the agent-browser skill do?
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill agent-browser-avibebuilder-claude-prime --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.