agent-browser

Automate browser interactions for testing and data extraction via CLI.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/derKlinke/codex-config --skill agent-browser-derklinke
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/derKlinke/codex-config/tree/main/skills/agent-browser
Command: npx skills add https://github.com/derKlinke/codex-config --skill agent-browser-derklinke

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser interactions for testing, form filling, and data extraction, reducing manual QA time and enabling repeatable workflows.

Core Features & Use Cases

  • Open URLs and navigate pages programmatically.
  • Snapshot the page to identify interactive elements via refs, then click, fill, or hover.
  • Take screenshots, extract text and data, and validate web app behavior across sessions.

Quick Start

Use the agent-browser CLI to open a page, snapshot DOM, interact with elements by their refs, and close the browser. agent-browser open https://example.com agent-browser snapshot -i agent-browser click @e1 agent-browser fill @e2 "sample text" agent-browser close

Frequently Asked Questions about agent-browser

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

FAQPage Schema
How do I automate browser interactions for web testing and data extraction?

Automate browser interactions by using a CLI-driven workflow to open URLs, snapshot the DOM, identify interactive elements via refs, and perform actions like clicking, filling, or hovering to capture results.

What is the process for identifying and interacting with elements during browser automation?

Identify interactive elements by taking a DOM snapshot, which assigns refs to elements. You then use these refs to programmatically click, fill form fields, or hover over them on dynamic web pages.

Can I use CLI commands to fill forms and take screenshots on dynamic web pages?

Yes, you can use CLI commands to open pages, fill forms using element refs, take screenshots, and extract text. This enables repeatable QA automation and data gathering workflows across sessions.

What's the best way to extract data and validate web app behavior across multiple sessions?

Validate web app behavior and extract data by opening URLs, snapshotting the DOM, interacting with elements, and capturing text or screenshots. This CLI-driven approach ensures repeatable workflows across sessions.

Do I need any external dependencies to run browser automation tasks with this tool?

No external dependencies are required to run browser automation tasks. The tool operates independently to open pages, snapshot the DOM, interact with elements, and close the browser.

Why does my browser automation workflow require taking a DOM snapshot before clicking elements?

A DOM snapshot is required because it identifies interactive elements and generates the specific refs needed to accurately target and click, fill, or hover over those elements on dynamic web pages.