agent-browser

Automate browser interactions for testing, form filling, and data extraction.

9|Updated Jan 19, 2026
One-click install
npx skills add https://github.com/gmoigneu/opencode-config --skill agent-browser-gmoigneu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/gmoigneu/opencode-config/tree/main/skills/agent-browser
Command: npx skills add https://github.com/gmoigneu/opencode-config --skill agent-browser-gmoigneu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser interactions for web testing, form filling, screenshots, and data extraction, enabling rapid, repeatable UI tasks without manual scripting.

Core Features & Use Cases

  • Browser automation for web testing, form filling, screenshots, and data extraction.
  • Snapshot and interaction workflow using element references or semantic locators for stable automation.
  • Real-world use cases include automated QA, data collection, and UI regression testing across websites.

Quick Start

Open a URL, capture a snapshot of interactive elements, and perform actions using element references.

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 without manual scripting?

Browser automation for web testing is achieved by opening a URL, capturing a snapshot of interactive elements, and performing actions using element references or semantic locators, enabling rapid and repeatable UI tasks.

Can I use semantic locators for stable browser automation across dynamic web pages?

Yes, stable browser automation across dynamic web pages uses a snapshot and interaction workflow that relies on semantic locators or element references to reliably target interactive elements during navigation.

What's the best way to automate form filling and data extraction across websites?

Automating form filling and data extraction is best handled through a command set that manages navigation, waits, and interactions, applying this workflow to data collection tasks and UI automation.

Do I need a browser automation runtime to handle navigation and waits for UI regression testing?

Yes, a browser automation runtime is required to handle navigation, waits, and interactions for UI regression testing, providing the necessary command set to automate tasks across dynamic web pages.

Why does browser automation fail on dynamic web pages and how do snapshots help?

Browser automation fails on dynamic web pages when elements shift during loading, but capturing element snapshots provides stable references that ensure interactions target the correct elements reliably.

When should I use end-to-end browser automation for QA pipelines instead of other tools?

End-to-end browser automation is ideal for QA pipelines when you need automated QA, data collection, and UI regression testing across websites, handling dynamic pages with snapshot-based interactions.