agent-browser

Automate browser navigation, form filling, data extraction, and screenshots via a CLI.

Updated Mar 8, 2026
One-click install
npx skills add https://github.com/AGIBuild/dotnet.CI.template --skill agent-browser-agibuild
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/AGIBuild/dotnet.CI.template/tree/main/.cursor/skills/agent-browser
Command: npx skills add https://github.com/AGIBuild/dotnet.CI.template --skill agent-browser-agibuild

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually interacting with websites for testing, scraping, or repetitive form entry is slow and error-prone. This Skill gives an AI agent a deterministic command-line interface to drive a real browser, so tasks like logging in, clicking through flows, and capturing page content become scripted and repeatable. ## Core Features & Use Cases - Snapshot-and-Ref Interaction: Get compact accessibility snapshots with element refs (@e1, @e2) to click, fill, select, and verify page elements without parsing raw HTML. - Session & State Management: Run isolated parallel sessions, save and restore authentication state, and persist cookies/localStorage across runs. - Capture & Extraction: Take full-page screenshots, save pages as PDF, record video of automation runs, and extract text or structured data. - Use Case: Automate a login flow once, save the auth state to a file, then reuse it in later runs to scrape a protected dashboard and capture a screenshot as evidence. ## Quick Start Ask the agent to open a website with agent-browser, snapshot the interactive elements, fill in the login form, and take a screenshot of the result.

Frequently Asked Questions about agent-browser

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate filling out a web form from the command line?▼

Open the page with agent-browser open, run agent-browser snapshot -i to get element refs, then use agent-browser fill on each input ref and agent-browser click on the submit button. Re-snapshot after submission to verify the result.

How do I keep a browser session logged in between automation runs?▼

After completing the login flow, run agent-browser state save auth.json to persist cookies and storage. In later runs, use agent-browser state load auth.json before navigating to restore the authenticated session.

Can agent-browser run multiple isolated browser sessions in parallel?▼

Yes, use the --session flag with distinct names to create isolated contexts with separate cookies, storage, and tabs. Each session is addressed independently, enabling concurrent scraping or A/B testing across sessions.

Why do my element refs stop working after clicking a button?▼

Refs are invalidated whenever the page changes, including navigation, form submissions, and dynamic content updates. Always run agent-browser snapshot -i again after any page change to obtain fresh refs before interacting.

Does agent-browser support mobile testing on iOS?▼

Yes, it supports iOS Simulator via the -p ios flag with a --device name, using the same snapshot and interaction workflow plus mobile gestures like tap and swipe. It requires macOS with Xcode and Appium with the xcuitest driver installed.

How do I avoid shell quoting issues when running JavaScript in the browser?▼

Use agent-browser eval --stdin with a heredoc or eval -b with base64-encoded scripts for anything containing nested quotes, template literals, or multiline code. Simple single-line expressions work with regular single-quoted eval.