agent-browser

Fetches live web pages as markdown and drives a real browser for interaction and verification.

Updated May 5, 2026
One-click install
npx skills add https://github.com/josippapez/ai-setup --skill agent-browser-josippapez
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/josippapez/ai-setup/tree/main/claude/plugins/dev-core/skills/agent-browser
Command: npx skills add https://github.com/josippapez/ai-setup --skill agent-browser-josippapez

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires agent-browser.

What problem does it solve? AI answers about external facts—library versions, API signatures, CLI flags, pricing, error messages—are often stale or hallucinated when recalled from memory. This Skill replaces guessing with live retrieval: it fetches the actual page as agent-readable text and can drive a real browser for interactive tasks. ## Core Features & Use Cases - Fact-finding via read: Fetch any URL as markdown, get heading outlines, filter sections, and discover docs through llms.txt indexes—ideal for checking current versions, changelogs, config keys, and spec wording. - Browser automation: Navigate pages, snapshot interactive elements as refs, fill forms, click buttons, take screenshots, and capture console logs or JS errors for testing web apps. - Authentication support: Import browser state, use persistent profiles, or named sessions to work with logged-in pages. - Use Case: Before answering "what is the latest version of library X and how do I configure its timeout option", run agent-browser read on the official docs, quote the exact option name, and cite the URL instead of relying on memory. ## Quick Start Ask the agent to look up the current documentation for a library or open a website and fill out a form, and it will fetch the live page or drive the browser with agent-browser commands.

Frequently Asked Questions about agent-browser

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

FAQPage Schema
How do I fetch a web page as markdown from the command line?

Run `agent-browser read <url>` to fetch a page as agent-readable text. It prefers markdown, retries with a .md suffix, walks up to the nearest llms.txt, and falls back to extracted HTML text.

How do I automate filling out a web form with a headless browser?

Open the page with `agent-browser open <url>`, run `agent-browser snapshot -i` to get interactive element refs like @e1, then use `agent-browser fill @e1 "value"` and `agent-browser click @e3` to submit.

How do I verify current library versions or API options instead of guessing?

Use `agent-browser read` on the official docs page, optionally with `--outline` or `--filter "term"` to locate the exact section. Quote the specific version or option name and cite the fetched URL.

Does agent-browser work with logged-in pages and authentication?

Yes. Import state from your existing browser with `--auto-connect state save`, use a persistent profile via `--profile <dir>`, or use `--session-name` to auto-save cookies and localStorage across runs.

When should I use a different tool instead of agent-browser?

Prefer narrower tools when they own the subject: repo-docs for repo conventions, opensrc for installed source code, context7 for library docs, accessibility for WCAG, and claude-api for Claude/Anthropic facts. Use agent-browser for live current web state.

Why do my element refs stop working after navigation?

Refs from a snapshot go stale after navigation or DOM changes. Re-run `agent-browser snapshot -i` after any page change to get fresh refs before interacting again.