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.
npx agentmods add skills/open-gsd/gsd-browser/npmnpx skills add open-gsd/gsd-browser --skill npmgit clone --depth 1 https://github.com/open-gsd/gsd-browserWrote 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.
[](https://agentmods.dev/skills/open-gsd/gsd-browser/npm)<a href="https://agentmods.dev/skills/open-gsd/gsd-browser/npm"><img src="https://agentmods.dev/badge/skills/open-gsd/gsd-browser/npm.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00180 | $0.07995 |
| Opus 5 | $0.00090 | $0.03998 |
| Sonnet 5 | $0.00036 | $0.01599 |
| Haiku 4.5 | $0.00018 | $0.00800 |
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 5d 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.
This is a copy
94% identical to gsd-browser — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 842 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Browser Automation with gsd-browser
Primary path for AI agents in 2026+: Use the MCP server — gsd-browser mcp.
It exposes 50+ tools, live resources (real snapshot/refs/state data), and executable prompts over stdio. All the unique strengths (versioned refs, live viewer + human collaboration/takeover/annotations/recordings, semantic intents, evidence bundles, self-healing action cache, batch execution, vault, visual regression, safety scanning, etc.) are available automatically to Cursor, Claude Desktop, VS Code + Copilot, and any other MCP client.
Quickstart for agents:
gsd-browser mcp
Then point your MCP client at it (see ./scripts/mcp-quickstart.sh cursor or claude/vscode for tailored configs).
Essential reading for MCP agents:
docs/mcp.md— Architecture, capabilities, client config examples, quickstart script.docs/AGENT-BEST-PRACTICES.md— Golden rules, recommended workflows (login, audit, human-in-the-loop, evidence, self-healing), "When to Use What" table, response envelope usage, prompt/resource patterns.docs/examples/mcp-client-config.json— Ready example.
The detailed command reference, error recovery, and workflow patterns in this SKILL.md document the exact semantics of the MCP tools (they are a direct 1:1 mapping). Use this as the source of truth when an MCP tool needs deeper clarification.
The installable curated skill pack lives in gsd-browser-skill/ (installed via the main installer or gsd-browser skill install).
Critical Rules (apply to both direct CLI and MCP usage)
- The daemon auto-starts on browser commands.
daemon healthonly reports state; it does not start a session. Usedaemon startonly when you want to pre-warm or verify daemon lifecycle explicitly. - Always re-snapshot after page changes. Refs are versioned (
@v1:e1). After navigation, form submission, or dynamic content loading, old refs are stale. Rungsd-browser snapshot(or read thegsd-browser://latest-snapshotMCP resource) to get fresh refs. - Use
--jsonwhen parsing output. Use text mode when reading output yourself. Use--jsonwhen you need to extract values programmatically (e.g., checking assertion results, parsing snapshot refs). MCP tools return rich envelopes containing structured_data. - Positional args have no flag prefix. Commands like
click,type,hovertake positional args — do NOT add--selector. See exact syntax in command reference below. (MCP equivalents:browser_click_refetc. takerefas a simple string param.) - Use
batchfor atomic multi-step flows. Batch reduces round trips and keeps pass/fail checks in one call. Use separate commands when you need intermediate output (e.g., snapshot to discover refs). MCP equivalent:browser_batch. - Use
viewwhen the user wants to watch or direct the browser. The live viewer is an authenticated local workbench with Control, Annotate, Record, and Sensitive modes. Keep CLI/MCP commands on the same named session. MCP tools:browser_view,browser_takeover,browser_annotation_request,browser_record_*,browser_goal, etc.
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.
- .npmignore 159 B
- AGENTS.md 2.4 KB
- bin/gsd-browser 745 B
- LICENSE-APACHE 11 KB
- LICENSE-MIT 1.1 KB
- package.json 1.4 KB
- README.md 15 KB
- scripts/build-package.js 1.8 KB runs code
- scripts/postinstall.js 5.5 KB runs code
- scripts/test-package.js 4.3 KB runs code
- scripts/verify-release-tag.js 826 B runs code
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.
- 5d ago First seen · 842 lines · 180 tokens per session scan A 82d90cdfe593
gsd-browser is a skill published in the GitHub repository open-gsd/gsd-browser (47 stars, last pushed today), licensed Apache-2.0. It adds 180 tokens to every session and 7,995 once invoked, about $0.0009 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to gsd-browser, differing in 46 lines, and is treated as a copy.
Other skills, from other repositories
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.