agent-browser
/agent-browser
Browser automation CLI built for AI agents - compact ref-based text output (200-400 tokens vs 3000-5000 for full DOM), native Rust, 50+ commands. Default browser-automation tool for the fleet. Use for any web navigation, scraping, form-filling, screenshots, or testing from the shell.
- Author
- S3YED ↗
- Repository
- appie-kit ↗
- Licence
- MIT
- Last repository change
- 26.08.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.08.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Browser automation CLI built for AI agents - compact ref-based text output (200-400 tokens vs 3000-5000 for full DOM), native Rust, 50+ commands. Default browser-automation tool for the fleet. Use for any web navigation, scraping, form-filling, screenshots, or testing from the shell.
Original author description
Browser automation CLI built for AI agents - compact ref-based text output (200-400 tokens vs 3000-5000 for full DOM), native Rust, 50+ commands. Default browser-automation tool for the fleet. Use for any web navigation, scraping, form-filling, screenshots, or testing from the shell.
How it works
- Install
- Core loop (ref-based)
- Why refs (the context win)
- What it covers (50+ commands)
- Architecture
- When to use vs other tools
SKILL.md preview
--- name: agent-browser description: Browser automation CLI built for AI agents - compact ref-based text output (200-400 tokens vs 3000-5000 for full DOM), native Rust, 50+ commands. Default browser-automation tool for the fleet. Use for any web navigation, scraping, form-filling, screenshots, or testing from the shell. --- # agent-browser - fleet default for browser automation A native-Rust browser-automation CLI designed for AI agents. Compact text output minimises context usage. Use it instead of heavier browser stacks for shell-driven web tasks. ## Install ```bash npm install -g agent-browser # all platforms # or: brew install agent-browser # macOS agent-browser install # download Chrome (first run only) # try without installing: npx agent-browser open example.com ``` ## Core loop (ref-based) ```bash agent-browser open example.com agent-browser snapshot -i # accessibility tree with refs: heading "..." [ref=e1], link "..." [ref=e2] agent-browser click @e2 # act on a ref from the snapshot agent-browser screenshot page.png agent-browser close ``` ## Why refs (the context win) `snapshot` returns a compact accessibility tree where each element has a ref (`@e1`, `@e2`): - Context-efficient: ~200-400 tokens vs ~3000-5000 for full DOM. - Deterministic: a ref points to the exact element from the snapshot (no fragile selectors). - Fast: no DOM re-query. AI-friendly: text output parses naturally. ## What it covers (50+ commands) Navigation, forms, screenshots, network control, storage/cookies/auth-state, file upload/download, tabs, frames, debugging. Built-in: video recording, streaming, profiler, diffing. First-class docs for React/Web Vitals, init scripts, and Next.js + Vercel. Stateful: sessions, profiles, proxy, security controls - good for long-running agents. ## Architecture Client-daemon: a Rust CLI talks to a native Rust daemon that drives Chrome over CDP. The daemon starts automatically and persists between commands. ## When to use vs other tools - **Default** for shell-driven browser work (cheapest context, deterministic). - Use Playwright/Stagehand only when you need their specific ecosystem features. - Cross-platform: macOS (arm64/x64), Linux (arm64/x64), Windows (x64). Works with: Claude Code, Cursor, Copilot, Codex, Gemini, opencode, and any agent that runs shell commands.
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · S3YED/appie-kit | 100 | MIT |
| vanducng/skills | 100 | MIT |
| mvschwarz/openrig | 100 | Apache-2.0 |
| mgiovani/cc-arsenal | 100 | MIT |
| desplega-ai/agent-swarm | 100 | MIT |
| nexu-io/open-design | 100 | Apache-2.0 |
| seaworld008/commonly-used-high-value-skills | 100 | MIT |
| slopus/happy | 100 | MIT |
| j62268781-alt/dsh-toolkit | 100 | MIT |
Database snapshot: 13.11.2026 · package version 6ea3169882a5 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 1 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100playwright-cli
Browser automation via Playwright CLI — UI testing, form filling, screenshots, scraping. Token-efficient alternative to MCP. Use when user asks to test UI, automate browser, take screenshots, fill forms, or scrape web pages. - 91browser-automation
Browser automation for web testing, scraping and AI agent interactions. Use for selectors, waiting strategies, and anti-detection patterns. - 100playwright
Provides Playwright-based browser automation and E2E testing. Supports screenshots, web scraping, and form automation. Use for "브라우저", "스크린샷", "E2E 테스트", "웹 스크래핑" requests. - 100playwright-cli
Browser automation via Playwright CLI for navigating pages, interacting with elements, capturing screenshots, and testing web applications through shell commands. Use when user mentions "playwright", "browser automation", "take a screenshot", "browser testing", "headless… - 100browser-automation
This skill should be used when the user asks to "build web automation scripts", "check browser automation for detection", "generate web scraping code", "create form filling automation", or "build anti-detection browser scripts". - 100browser
Minimal Chrome DevTools Protocol tools for browser automation and scraping. Use when you need to start Chrome, navigate pages, execute JavaScript, take screenshots, or interactively pick DOM elements. Triggers include "browse website", "scrape page", "take screenshot", "automate…