A browser-automation skill for controlling Chrome or Chromium. It supports actions such as opening pages, entering information, clicking controls, taking screenshots, checking results, and extracting structured data.

Use it to inspect local or live websites, complete browser workflows, test forms, capture evidence, compare visual changes, and debug browser-based agent tasks.

It lets an agent test and inspect real web pages instead of relying only on source code or assumptions. Re-snapshotting after page changes keeps its page references current.

gsd-browser — Skill for Claude Code by open-gsd

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add open-gsd/gsd-browser --skill gsd-browser-skill

Clone the repo

git clone --depth 1 https://github.com/open-gsd/gsd-browser

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/open-gsd/gsd-browser/gsd-browser-skill/github.svg)](https://agentmods.dev/skills/open-gsd/gsd-browser/gsd-browser-skill)

Your own site

<a href="https://agentmods.dev/skills/open-gsd/gsd-browser/gsd-browser-skill"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-browser/gsd-browser-skill/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/open-gsd/gsd-browser/gsd-browser-skill"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-browser/gsd-browser-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 175 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,032 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00175	$0.02032
Opus 5.5	$0.00070	$0.00813
Sonnet 5.5	$0.00035	$0.00406
Haiku 4.5	$0.00017	$0.00203

Measured 2mo ago against content hash f3d8b354d5b3, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

gsd-browser scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

gsd-browser-skill/SKILL.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

<essential_principles>

Primary path for AI agents (2026+): Use gsd-browser mcp (the stdio MCP server). It exposes 50+ tools, live resources (latest-snapshot, current-state, active-recordings, timeline, etc.), and executable prompts (robust_login_flow, full_page_audit, autonomous_research_task, evidence_creation_workflow, debug_stuck_agent_flow, etc.) with rich agent-optimized envelopes (summary + structured_data + suggested_next_actions + evidence_refs).

For MCP clients (Cursor, Claude Desktop, VS Code + Copilot, etc.): After connecting to gsd-browser mcp, read the root docs/AGENT-BEST-PRACTICES.md (golden rules, workflows, "When to Use What" table) and docs/mcp.md. Run ./scripts/mcp-quickstart.sh cursor (or claude/vscode) for tailored config.

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 (or read the gsd-browser://latest-snapshot MCP resource) to get fresh refs before interacting with _ref tools.

Use --json when parsing output. Use text mode when reading output yourself. Use --json when you need to extract values programmatically. MCP tools return rich structured envelopes.

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 (or read latest-snapshot resource) -> interact (prefer semantic act/find_best first, then refs) -> re-snapshot (after DOM changes). For complex flows, prefer browser_batch via MCP.

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 "[email protected]"
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). MCP agents: use browser_batch for atomic multi-step execution.

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 + annotation + record capabilities. Keep using CLI/MCP commands for actions; the viewer is the shared screen and control surface. MCP tools: browser_view, browser_takeover, browser_annotation_request, browser_record_start/stop, browser_goal, browser_step, etc. These are among the highest-leverage collaborative features.

Global options available on all commands:

Flag	Purpose
`--json`	Structured 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 + persistent action cache / state (highly recommended for MCP agents)
`--no-narration-delay`	Skip narration lead-time sleeps while keeping history/events

</essential_principles>

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

User intent	Workflow
Navigate, click, type, fill forms, interact with pages (MCP or CLI)	`workflows/navigate-and-interact.md`
Share the browser screen, narrate actions, pause/step/resume/abort, human collaboration + evidence	`workflows/live-viewer-and-narration.md`
Scrape data, extract content, read page structure	`workflows/scrape-and-extract.md`
Test pages, run assertions, visual regression, mock network	`workflows/test-and-assert.md`
Debug issues, check logs, diagnose problems (use debug_bundle + MCP prompts)	`workflows/debug-and-diagnose.md`
Install, configure, set up sessions, MCP client setup	`workflows/setup-and-configure.md`

Read the full file on GitHub · 133 lines

Files

What ships with it

11 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2mo ago First seen · 133 lines · 175 tokens per session scan A f3d8b354d5b3

Subscribe to this mod's changes

gsd-browser is a skill published in the GitHub repository open-gsd/gsd-browser (57 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 175 tokens to every session and 2,032 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Browser automation

gsd-browser next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
gsd-browseropen-gsd/gsd-browser	Skill	57	1mo ago	Apache-2.0	A	175	Claude Code
interactive-loginyc-software/qm	Skill	16k	yesterday	MIT	A	46	Claude Code, Codex
pinchtab-mcppinchtab/pinchtab	Skill	11k	10d ago	MIT	A	52	Claude Code, Codex
azure-messaging-webpubsub-javamicrosoft/skills	Skill	3.2k	yesterday	MIT	A	43	Claude Code
cua-driverdavidondrej/skills	Skill	4.3k	3d ago	MIT	A	68	Claude Code, Codex
open-design-browsercompozy/compozy	Skill	2.8k	yesterday	MIT	A	56	Claude Code, Codex
southwestborski/travel-hacking-toolkit	Skill	895	yesterday	MIT	A	40	Claude Code