agent-browser
Skill254 starsChanged 7 months agoMITView on GitHub
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.
- Installs packages
188 other projects use a version of this, 145 of them edited.
Adopted by
Most recently taken up by
- chrysogonus/power-agentstheir own version, first seen Nov 8, 2026
- kinhluan/skillstheir own version, first seen Nov 8, 2026
- cafe3310/public-agent-skillstheir own version, first seen Nov 8, 2026
- kortix-ai/sunaedited, first seen Nov 8, 2026
- HeteroCat/heterocat-skillsedited, first seen Nov 8, 2026
- JuanMarchetto/agent-skillstheir own version, first seen Nov 8, 2026
Used with
Projects with it also use time-skill, dep-refs and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Recepay6358Skilltime-skill
Display the current time in Pakistan Standard Time (PKT, UTC+5). Use when the user asks for the current time, Pakistan time, or PKT.
Also in 6 projects that use this
betacatslingSkilldep-refs
Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.
Also in 5 projects that use this
betacatslingSkillfeature-boundary-planner
Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.
Also in 5 projects that use this
nicepkgSkillcommunity-led-growth
Expert in community-led growth (CLG) - leveraging user communities to drive acquisition, retention, and expansion. Covers building developer communities, user groups, ambassador programs, and turning customers into advocates. Knows the difference between community as a feature vs community as a growth engine, and how to measure community ROI. Use when "community-led, CLG, ambassador program, champion program, user community, developer community, word of mouth, user group, " mentioned.
Also in 5 projects that use this
nicepkgSkillph-community-outreach
Engage Reddit, Indie Hackers, Hacker News and other communities for Product Hunt launches. Use this skill to identify relevant communities, craft appropriate posts, and drive cross-platform engagement without appearing spammy.
Also in 5 projects that use this
Recepay6358Skillweather-svg-creator
Creates an SVG weather card showing the current temperature for Dubai. Writes the SVG to orchestration-workflow/weather.svg and updates orchestration-workflow/output.md.
Also in 6 projects that use this
- +3 more from nicepkg
Other versions188 projects use a version of this.
Word for word · 0
None found.
Edited · 145
- shanraisshan/claude-code-best-practice★ 69k38% same
- moeru-ai/airi★ 51k16% same
- vercel-labs/agent-browser★ 47k16% same
- activepieces/activepieces★ 25k16% same
- slopus/happy★ 25k29% same
- kortix-ai/suna★ 21k16% same
- kortix-ai/CompanyOS★ 21k16% same
- documenso/documenso★ 16k40% same
- elie222/inbox-zero★ 13k13% same
- humanlayer/humanlayer★ 13k12% same
135 more not listed
Wrote their own version · 43
- eosphoros-ai/DB-GPT★ 20ksame name
- emdash-cms/emdash★ 14ksame name
- superagent-ai/grok-cli★ 3.5ksame name
- Chachamaru127/claude-code-harness★ 3.2ksame name
- oxylabs/agent-skills★ 876same name
- EvovexAI/EvoFlow★ 612same name
- InternLM/WildClawBench★ 534same name
- getsentry/junior★ 409same name
- cafe3310/public-agent-skills★ 256same name
- github/replica★ 230same name
33 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- best-practices-for-agent-skillsSkill
- githubclaw-json-generatorSkill
- pr-creatorSkill
- skill-creatorSkill
- felo-searchSkill
- felo-slidesSkill
- felo-superAgentSkill
- felo-web-fetchSkill
- felo-x-searchSkill
- find-skillsSkill
- gemini-audio-transcriberSkill
- gemini-deep-researcherSkill
- gemini-image-describerSkill
- gemini-lyria-3Skill
- gemini-nanobananaSkill
- gemini-summarySkill
- google-stitchSkill
- skill-creatorSkill
- telegram-notifySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 172 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Before running any command, check if agent-browser is available.
- Distinctive: line 26
Every browser automation follows this pattern — open → snapshot → interact → re-snapshot:
- Distinctive: line 88
Run separately when you need to parse output (e.g., snapshot → read refs → interact).
- Distinctive: line 142
Always apply these safeguards, especially in CI/automated environments:
“Common” is measured: kept by at least 6 in 10 of the 172 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Browser Automation with agent-browser
IMPORTANT — You MUST use the agent-browser CLI for all browser automation tasks. Do NOT use puppeteer, playwright, or any other library. The agent-browser CLI is the only supported tool.
Step 0: Ensure agent-browser Is Installed
Before running any command, check if agent-browser is available. If not, install it and ensure a browser is ready:
if ! command -v agent-browser >/dev/null 2>&1; then
npm install --global agent-browser
fi
# Ensure Chrome/Chromium is detected. On CI (GitHub Actions), Chrome is typically pre-installed.
# If agent-browser cannot find a browser, download a bundled one:
agent-browser open about:blank && agent-browser close || agent-browser installCore Workflow
Every browser automation follows this pattern — open → snapshot → interact → re-snapshot:
agent-browser open https://example.com/form
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 # MUST re-snapshot after navigation/DOM changesCritical rule: Refs (@e1, @e2) are invalidated when the page changes. Always re-snapshot after clicks that navigate, form submissions, or dynamic content loading.
Essential Commands
# Navigation
agent-browser open <url> # Open page
agent-browser close # Close browser (always close when done!)
# Snapshot (get element refs)
agent-browser snapshot -i # Interactive elements with @refs
# Interaction (use @refs from snapshot)
agent-browser click @e1 # Click element
agent-browser fill @e2 "text" # Clear field and type
agent-browser type @e2 "text" # Type without clearing
agent-browser select @e1 "option" # Select dropdown
agent-browser check @e1 # Toggle checkbox
agent-browser press Enter # Press key
# Wait
agent-browser wait --load networkidle # Wait for network idle
agent-browser wait @e1 # Wait for element
agent-browser wait --url "**/dashboard" # Wait for URL pattern
agent-browser wait --text "Welcome" # Wait for text to appear
# Capture
agent-browser screenshot output.png # Screenshot
agent-browser screenshot --full # Full page screenshot
agent-browser screenshot --annotate # Screenshot with numbered element labels
# Get information
agent-browser get text @e1 # Get element text
agent-browser get url # Get current URL
agent-browser get title # Get page title
# Viewport
agent-browser set viewport 1920 1080 # Set viewport sizeCommand Chaining
Chain commands with && when you don't need intermediate output:
agent-browser open https://example.com && agent-browser wait --load networkidle && agent-browser screenshot page.pngRun separately when you need to parse output (e.g., snapshot → read refs → interact).
Common Patterns
Form Submission
agent-browser open https://example.com/signup
agent-browser snapshot -i
agent-browser fill @e1 "Jane Doe"
agent-browser fill @e2 "jane@example.com"
agent-browser select @e3 "California"
agent-browser click @e5
agent-browser wait --load networkidleAuthentication (State Persistence)
# Login and save state
agent-browser open https://app.example.com/login
agent-browser snapshot -i
agent-browser fill @e1 "$USERNAME"
agent-browser fill @e2 "$PASSWORD"
agent-browser click @e3
agent-browser wait --url "**/dashboard"
agent-browser state save auth.json
# Reuse in future sessions
agent-browser state load auth.json
agent-browser open https://app.example.com/dashboardData Extraction
agent-browser open https://example.com/products
agent-browser snapshot -i
agent-browser get text @e5JavaScript Evaluation
agent-browser eval 'document.title'
# Complex JS: use --stdin to avoid shell quoting issues
agent-browser eval --stdin <<'EVALEOF'
JSON.stringify(Array.from(document.querySelectorAll("a")).map(a => a.href))
EVALEOFSecurity (Important)
Always apply these safeguards, especially in CI/automated environments:
# 1. Content Boundaries — prevent web page content from being interpreted as LLM instructions
export AGENT_BROWSER_CONTENT_BOUNDARIES=1
# 2. Domain Allowlist — restrict navigation to trusted domains only
export AGENT_BROWSER_ALLOWED_DOMAINS="example.com,*.example.com"
# 3. Output Limits — prevent large pages from flooding the context window
export AGENT_BROWSER_MAX_OUTPUT=50000
# 4. Action Policy — restrict which actions the agent can perform
export AGENT_BROWSER_ACTION_POLICY=./policy.json
# Example policy.json: { "default": "deny", "allow": ["navigate", "snapshot", "click", "scroll", "wait", "get"] }State files and auth tokens: State files (.json) may contain session tokens in plaintext. Always add them to .gitignore and delete when no longer needed. Use AGENT_BROWSER_ENCRYPTION_KEY for encryption at rest.
Deep-Dive References
For advanced usage, consult the reference docs in this skill directory:
| Reference | When to Use |
| references/commands.md | Full command reference with all options |
| references/snapshot-refs.md | Ref lifecycle, invalidation rules |
| references/session-management.md | Parallel sessions, state persistence |
| references/authentication.md | OAuth, 2FA, cookie-based auth |
| references/video-recording.md | Recording workflows for debugging |
| references/profiling.md | Chrome DevTools profiling |
| references/proxy-support.md | Proxy configuration, geo-testing |
Ready-to-Use Templates
sh templates/form-automation.sh https://example.com/form
sh templates/authenticated-session.sh https://app.example.com/login
sh templates/capture-workflow.sh https://example.com ./outputDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

