browser-tools

browser-tools is a skill for Claude Code from lttr/claude-marketplace. It costs 60 tokens per session (1,219 once invoked), scanned A, original, MIT.

A browser-automation skill for controlling Chrome through its debugging connection.

In plain words
What is it for?
It helps test websites, navigate pages, run page scripts, select elements, scrape information, and capture screenshots.
Why use it?
It gives an agent a way to inspect and interact with web pages when ordinary code inspection is not enough.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

Part of the browser-tools plugin — 1 skill, 1 command shipped together

Good fit It helps test websites, navigate pages, run page scripts, select elements, scrape information, and capture screenshots.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/lttr/claude-marketplace/browser-tools
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 lttr/claude-marketplace --skill browser-tools
Clone the repo
git clone --depth 1 https://github.com/lttr/claude-marketplace

Made for: Claude Code.

Or install browser-tools, the plugin that ships this one along with the rest of its 1 skill, 1 command.

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.

agentmods badge for browser-tools

README.md
[![agentmods](https://agentmods.dev/badge/skills/lttr/claude-marketplace/browser-tools/github.svg)](https://agentmods.dev/skills/lttr/claude-marketplace/browser-tools)
Your own site
<a href="https://agentmods.dev/skills/lttr/claude-marketplace/browser-tools"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/browser-tools/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.

agentmods 80×15 button for browser-tools

Your own site · 80×15
<a href="https://agentmods.dev/skills/lttr/claude-marketplace/browser-tools"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/browser-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 60 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,219 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.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00060 $0.01219
Opus 5 $0.00030 $0.00609
Sonnet 5 $0.00012 $0.00244
Haiku 4.5 $0.00006 $0.00122

Measured 10d ago against content hash 38162166b1bd, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

browser-tools 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 10d ago.

The scan reads SKILL.md. This mod also ships 7 executable files (scripts/browser-console.js, scripts/browser-cookies.js, scripts/browser-eval.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

_archived/browser-tools/skills/browser-tools/SKILL.md · 174 lines

How it starts

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

Browser Tools

Chrome DevTools Protocol automation for agent-assisted web testing and interaction. Uses Chrome running on :9222 with remote debugging.

Prerequisites

Run /browser-tools:setup once after plugin installation - This installs dependencies and creates global symlinks for all browser scripts.

Usage

When user asks to test, verify, or interact with web pages using browser tools:

  1. Start Chrome - Launch with debugging enabled
  2. Navigate & interact - Use scripts to navigate, evaluate JS, take screenshots
  3. Return results - Show output/screenshots to user

IMPORTANT: Use command names directly (e.g., browser-start), NOT full paths (e.g., ~/bin/browser-start). Commands are in PATH after setup.

Available Scripts

All scripts located in ${CLAUDE_SKILL_DIR}/scripts/:

browser-start

By default use the persistent profile at /tmp/chrome-profile-browser-tools.

browser-start --profile    # Persistent profile
browser-start              # Fresh profile

Launch Chrome with remote debugging on port 9222. Use --profile to maintain login state between sessions.

browser-nav

browser-nav https://example.com
browser-nav https://example.com --new

Navigate to URLs. Use --new to open in new tab instead of current tab.

browser-eval

browser-eval 'document.title'
browser-eval 'document.querySelectorAll("a").length'
browser-eval 'Array.from(document.querySelectorAll("h1")).map(h => h.textContent)'

Execute JavaScript in active tab. Runs in async context. Use for:

  • Extract data from pages
  • Inspect page state
  • Manipulate DOM
  • Test page functionality

browser-screenshot

browser-screenshot

Capture current viewport, returns temp file path. Use Read tool to show screenshot to user.

browser-pick

browser-pick                      # Uses default message "Select element(s)"
browser-pick "Select the submit button"

Interactive element picker - Launches UI overlay for user to click and select elements. Returns element details (tag, id, class, text, html, parent hierarchy). Message parameter is optional.

Read the full file on GitHub · 174 lines

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.

  1. 10d ago First seen · 174 lines · 60 tokens per session scan A 38162166b1bd

Subscribe to this mod's changes

browser-tools is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 3d ago), licensed MIT. It adds 60 tokens to every session and 1,219 once invoked, about $0.0003 per session on Opus 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-31.

Related

Other skills, from other repositories

web2-vuln-classes

Complete reference for 26 web2 bug classes with root causes, detection patterns, bypass tables, exploit techniques, and real paid examples. Covers IDOR, auth bypass, XSS, SSRF (11 IP bypass techniques), SQLi, business logic, race conditions, OAuth/OIDC, file upload (10 bypass techniques), GraphQL, LLM/AI (ASI01-ASI10…

Awarexone/Agentic-Bug-Hunter · 351 tokens

playwright-cli

Automates browser interactions for web testing, form filling, screenshots, and data extraction using playwright-cli. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, extract information from web pages, mock network requests, manage browser…

zebbern/claude-code-guide · 67 tokens

scrapling

A Python-based web-scraping workflow for fetching pages and extracting data, including pages that need JavaScript, login sessions, or protection handling. Web scraping means collecting information from websites by code.

fengshao1227/ccg-workflow · 74 tokens

browser

Browser automation — setup the bsession environment, fetch info from a website (one-shot), create scripted automations (one-shot or recurring), or debug existing sessions. Works from any repo.

UnicomAI/wanwu · 40 tokens

agent-browser

Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection.

UnicomAI/wanwu · 21 tokens

playwright-skill

Battle-tested Playwright patterns for E2E, API, component, visual, accessibility, and security testing. Covers locators, fixtures, POM, network mocking, auth flows, debugging, CI/CD (GitHub Actions, GitLab, CircleCI, Azure, Jenkins), framework recipes (React, Next.js, Vue, Angular), and migration guides from…

zebbern/claude-code-guide · 87 tokens