Agent skill

Gsd Browser

by gsd-build in gsd-build/gsd-browser

Native Rust browser automation CLI for AI agents. An agent skill from gsd-build/gsd-browser.

Apache-2.0Auto-check passedProductivity & Automation

Install Gsd Browser

skills CLI
$ npx skills add gsd-build/gsd-browser --skill gsd-browser -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install gsd-build/gsd-browser gsd-browser --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/gsd-build/gsd-browser.git skills-src && mkdir -p .claude/skills && cp -r skills-src/gsd-browser-skill .claude/skills/gsd-browser && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
gsd-browser
GitHub stars
268
Token cost
~1.3k tokens
SKILL.md length
453 words
Files
12 (incl. references)
Skills in repo
2
Repo updated
First seen
Licence
Apache-2.0

At a glance

Native Rust browser automation CLI for AI agents. An agent skill from gsd-build/gsd-browser.

  • The user needs to interact with websites
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Take screenshots
  • Share a live browser view

What it does

Gsd Browser is an agent skill from gsd-build/gsd-browser. Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites, navigate pages, fill forms, click buttons, take screenshots, share a live browser view, narrate browser actions, extract structured data, run assertions, test web apps, mock network requests, or automate any browser task. Triggers include "open a website", "fill out a form", "take a screenshot", "show me the browser", "share the screen", "pause the browser", "step through this", "scrape data", "test this web app"…

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 13 other files, including reference files (for example `references/command-reference.md`, `references/configuration.md` and `references/error-recovery.md`).

It sits in Productivity & Automation, covering Browser automation, Visual regression testing and Web scraping. It works with Rust. The repository describes itself as: A fast, native browser automation CLI built from the ground up for AI agents, powered by Chrome DevTools Protocol. 63 commands covering navigation, interaction, screenshots… The licence is Apache-2.0.

When your agent uses it

  • The user needs to interact with websites
  • Take screenshots
  • Share a live browser view
  • Narrate browser actions

Example prompts

  • “open a website”
  • “fill out a form”
  • “take a screenshot”
  • “/gsd-browser”

Requirements

  • Pre-approved tools (allowed-tools): Bash(gsd-browser:*), Bash(gsd-browser *)

What it can do on your machine

Read from SKILL.md and the folder at commit e5ec085. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Bash(gsd-browser:*)
    • Bash(gsd-browser *)

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are bash).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Gsd Browser loads about 1.3k tokens when it runs, and up to ~6.9k if it reads all its reference files. Until then it costs about 157 tokens; SKILL.md has 453 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~157
When it runs · the whole SKILL.md, loaded when a task matches
~1.3k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from gsd-build/gsd-browser at commit e5ec085, republished under its Apache-2.0 licence (© gsd-build). 453 words, ~1,283 tokens.

Download SKILL.mdSave it as .claude/skills/gsd-browser/SKILL.md (or your agent's skills folder). This skill also uses 11 other files; get the full folder from GitHub.
name
gsd-browser
description
Native Rust browser automation CLI for AI agents. Use when the user needs to interact with websites, navigate pages, fill forms, click buttons, take screenshots, share a live browser view, narrate browser actions, extract structured data, run assertions, test web apps, mock network requests, or automate any browser task. Triggers include "open a website", "fill out a form", "take a screenshot", "show me the browser", "share the screen", "pause the browser", "step through this", "scrape data", "test this web app", "login to a site", "visual regression test", or any task requiring programmatic web interaction.
allowed-tools
Bash(gsd-browser:*), Bash(gsd-browser *)

<essential_principles>

The daemon auto-starts on browser commands. gsd-browser daemon health reports state and does not start a session. Use gsd-browser daemon start only when you want to pre-warm or verify daemon lifecycle explicitly.

Always re-snapshot after page changes. Refs are versioned (@v1:e1, @v2:e3). After navigation, form submission, or dynamic content loading, old refs are stale. Run gsd-browser snapshot to get fresh refs before interacting.

Use --json when parsing output. Use text mode when reading output yourself. Use --json when you need to extract values programmatically.

Positional args have no flag prefix. Commands like click, type, hover take positional args. Do NOT add --selector:

  • gsd-browser click "button.submit" (correct)
  • gsd-browser click --selector "button.submit" (WRONG)

Core workflow pattern: Every browser automation follows: navigate -> snapshot -> interact -> re-snapshot (after DOM changes).

bash
gsd-browser navigate https://example.com
gsd-browser snapshot
# Read snapshot output: @v1:e1 [input type="email"], @v1:e2 [button] "Submit"
gsd-browser fill-ref @v1:e1 "user@example.com"
gsd-browser click-ref @v1:e2
gsd-browser wait-for --condition network_idle
gsd-browser snapshot  # REQUIRED - old refs are now stale

Command chaining: Use && when you don't need intermediate output. Run separately when you need to parse output first (e.g., snapshot to discover refs, then interact).

Use the live viewer when the user wants to watch or direct the browser. gsd-browser view opens a localhost viewer with live frames, narrated action history, ref overlays, and pause/step/resume/abort controls. Keep using CLI commands for actions; the viewer is the shared screen and control surface.

Global options available on all commands:

FlagPurpose
--jsonStructured JSON output
--browser-path <path>Path to Chrome/Chromium
--cdp-url <url>Attach to an already-running Chrome instance
--session <name>Named session for parallel instances
--no-narration-delaySkip narration lead-time sleeps while keeping history/events

</essential_principles>

<routing>

Based on what the user needs, read the appropriate workflow:

User intentWorkflow
Navigate, click, type, fill forms, interact with pagesworkflows/navigate-and-interact.md
Share the browser screen, narrate actions, pause/step/resume/abortworkflows/live-viewer-and-narration.md
Scrape data, extract content, read page structureworkflows/scrape-and-extract.md
Test pages, run assertions, visual regression, mock networkworkflows/test-and-assert.md
Debug issues, check logs, diagnose problemsworkflows/debug-and-diagnose.md
Install, configure, set up sessionsworkflows/setup-and-configure.md
Show full SKILL.md (154 more words)Show less

After reading the workflow, follow it. Load references only when the workflow directs you to.

</routing>

<reference_index>

All domain knowledge in references/:

Commands: command-reference.md (complete command syntax) Snapshots: snapshot-and-refs.md (versioned refs, snapshot modes) Intents: semantic-intents.md (15 predefined intents for find-best/act) Errors: error-recovery.md (common errors and fixes) Config: configuration.md (TOML config, env vars, 5-layer merge)

</reference_index>

<workflows_index>

WorkflowPurpose
navigate-and-interact.mdPage navigation, clicking, typing, forms, intents
live-viewer-and-narration.mdLive shared viewer, narrated history, refs overlay, controls
scrape-and-extract.mdData extraction, accessibility tree, page source
test-and-assert.mdAssertions, visual regression, network mocking, test generation
debug-and-diagnose.mdConsole/network logs, timeline, debug bundles
setup-and-configure.mdInstallation, configuration, sessions, daemon management

</workflows_index>

<success_criteria>

Browser automation task is complete when:

  • Target page state is achieved and verified (via assertions or visual confirmation)
  • Daemon is stopped if no further browser work is needed (gsd-browser daemon stop)
  • Extracted data is returned in the expected format
  • Any saved state (auth, cookies) is persisted for reuse if appropriate

</success_criteria>

© gsd-build, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 11 other files (references) in gsd-browser-skill of gsd-build/gsd-browser.

  • SKILL.md
  • references/command-reference.md
  • references/configuration.md
  • references/error-recovery.md
  • references/semantic-intents.md
  • references/snapshot-and-refs.md
  • workflows/debug-and-diagnose.md
  • workflows/live-viewer-and-narration.md
  • workflows/navigate-and-interact.md
  • workflows/scrape-and-extract.md
  • workflows/setup-and-configure.md
  • workflows/test-and-assert.md

Open the folder on GitHubat commit e5ec085

Compare with similar skills

Gsd Browser next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Gsd Browser compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Gsd Browser this skillgsd-build/gsd-browser268—~1.3kAutomated safety check: PassApache-2.0
Browser Automationalirezarezvani/claude-skills28k—~3.4kAutomated safety check: NotesMIT
Browser Useaiskillstore/marketplace430—~1.1kAutomated safety check: PassNone
Browserwingbrowserwing/browserwing1.4k—~1.8kAutomated safety check: PassMIT
Bright Data MCPbrightdata/skills2641 repos~3.7kAutomated safety check: PassMIT
Scrapingbee CLIScrapingBee/scrapingbee-cli108—~3.2kAutomated safety check: NotesMIT

Similar skills

  • Browser Automation

    alirezarezvani/claude-skills

    A skill your agent uses when the user asks to automate browser tasks, scrape websites, fill forms, capture screenshots, extract structured data from web pages, or build web automation workflows.

    28k GitHub stars~3.4k tokensUpdated 1 mo ago
    Productivity & AutomationAuto-check: notes
  • Browser Use

    aiskillstore/marketplace

    Browser automation using Playwright MCP. An agent skill from aiskillstore/marketplace.

    430 GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed
  • Browserwing

    browserwing/browserwing

    Browser automation platform with 78 built-in scripts and full CLI.

    1.4k GitHub stars~1.8k tokensUpdated 2 mo ago
    Productivity & AutomationAuto-check passed
  • Bright Data MCP

    brightdata/skills

    Bright Data MCP handles ALL web data operations. An agent skill from brightdata/skills.

    264 GitHub starsUsed in 1 repo~3.7k tokens
    Productivity & AutomationAuto-check passed
  • Scrapingbee CLI

    ScrapingBee/scrapingbee-cli

    Fetch and read any web page, search the web, crawl a site, or pull structured data out of pages.

    108 GitHub stars~3.2k tokensUpdated 2 days ago
    Productivity & AutomationAuto-check: notes
  • Agent

    tinyfish-io/tinyfish-cookbook

    Default browser automation agent — click, fill forms, navigate, log in, and extract structured data from any website using a natural-language goal, or run the same task across multiple sites in…

    2.2k GitHub stars~1.1k tokensUpdated today
    Testing & QAAuto-check passed

More from gsd-build/gsd-browser

  • Gsd Browser

    gsd-build/gsd-browser

    Native Rust browser automation CLI for AI agents. An agent skill from gsd-build/gsd-browser.

    268 GitHub stars~7.5k tokensUpdated 5 mo ago
    Auto-check passed

Works with

Questions about Gsd Browser

What does Gsd Browser do?

Native Rust browser automation CLI for AI agents. An agent skill from gsd-build/gsd-browser. Gsd Browser is an agent skill from gsd-build/gsd-browser. Native Rust browser automation CLI for AI agents.

When should I use Gsd Browser?

Gsd Browser fits situations like: the user needs to interact with websites; take screenshots; share a live browser view; narrate browser actions.

How do I install Gsd Browser in Claude Code?

Run `npx skills add gsd-build/gsd-browser --skill gsd-browser -a claude-code`. Or copy the skill folder (gsd-browser-skill in gsd-build/gsd-browser) into .claude/skills/gsd-browser in your project. Claude Code loads it when a task matches its description.

How do I install Gsd Browser in Codex?

Run `npx skills add gsd-build/gsd-browser --skill gsd-browser -a codex`. Or copy the skill folder (gsd-browser-skill in gsd-build/gsd-browser) into .agents/skills/gsd-browser in your project. Codex loads it when a task matches its description.

Can I use Gsd Browser in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add gsd-build/gsd-browser --skill gsd-browser -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/gsd-browser, .gemini/skills/gsd-browser, .github/skills/gsd-browser and .opencode/skills/gsd-browser in your project.

What does Gsd Browser need to run?

SKILL.md names no scripts, command-line tools or credentials: Gsd Browser is instructions for the agent only. Its frontmatter pre-approves these tools: Bash(gsd-browser:*), Bash(gsd-browser *).

Does Gsd Browser access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Gsd Browser safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Gsd Browser use?

Gsd Browser is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Gsd Browser use?

About 1.3k tokens (SKILL.md is roughly 5.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.6k tokens, read only when the agent opens those files.

What are the alternatives to Gsd Browser?

Skills that share tags, products or a category with Gsd Browser: Browser Automation (alirezarezvani/claude-skills, 28k stars), Browser Use (aiskillstore/marketplace, 430 stars), Browserwing (browserwing/browserwing, 1.4k stars) and Bright Data MCP (brightdata/skills, 264 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Gsd Browser?

gsd-build (a GitHub organization) maintains it in gsd-build/gsd-browser, which has 268 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on May 3, 2026.

Source: gsd-build/gsd-browser on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.