agent-browser

Automate browser interactions with agent-browser commands for navigation, form filling, and data extraction.

25|5|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/deadlock-api/deadlock-api --skill agent-browser-deadlock-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/deadlock-api/deadlock-api/tree/main/website/.agents/skills/agent-browser
Command: npx skills add https://github.com/deadlock-api/deadlock-api --skill agent-browser-deadlock-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Browser automation for AI agents to interact with websites, including navigating pages, filling forms, taking screenshots, extracting data, testing web apps, and automating browser tasks.

Core Features & Use Cases

  • Navigate to URLs and snapshot the DOM to identify interactive elements
  • Interact with elements via click, fill, select, and type commands, enabling end-to-end automation
  • Capture data and visuals via screenshots, text extraction, and PDF output for reporting

Quick Start

Open a URL with agent-browser and begin automating interactions by taking a snapshot and performing actions in sequence.

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 AI workflows?

Automate browser interactions by issuing sequential commands to navigate URLs, fill forms, click elements, and extract data. This enables end-to-end automation for tasks like form submission, authentication flows, and data collection within single or multi-step sessions.

What is the best way to extract data from web pages for automated collection?

Data extraction from web pages is handled by navigating to the target URL, taking a DOM snapshot to identify elements, and using text extraction commands. You can also capture visual reports via screenshots and PDF output during the automation session.

Do I need a local Chromium-based browser to run web automation commands?

Yes, a local Chromium-based browser is required to execute web automation commands. The tool relies on this environment to maintain per-session state and perform interactions like opening pages, filling forms, and taking screenshots.

Can I handle authentication flows and form filling in multi-step browser sessions?

Yes, authentication flows and form filling are supported in multi-step sessions. The command surface includes open, fill, click, and wait operations, allowing you to manage per-session state and complete complex end-to-end automation sequences.

Does web automation testing support visual validation with screenshots and PDF output?

Web automation testing supports visual validation through screenshot and PDF output commands. You can capture the visual state of pages during single or multi-step sessions to verify rendering and interactive elements.

Why does my browser automation task need a DOM snapshot before clicking elements?

A DOM snapshot is needed to identify interactive elements before clicking. By capturing the page structure first, the automation tool can accurately target elements for subsequent fill, select, and type commands in the workflow.