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 skills add lttr/claude-marketplace --skill browser-toolsgit clone --depth 1 https://github.com/lttr/claude-marketplaceWrote 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/lttr/claude-marketplace/browser-tools)<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.
<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>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.00060 | $0.01219 |
| Opus 5 | $0.00030 | $0.00609 |
| Sonnet 5 | $0.00012 | $0.00244 |
| Haiku 4.5 | $0.00006 | $0.00122 |
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.
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.
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:
- Start Chrome - Launch with debugging enabled
- Navigate & interact - Use scripts to navigate, evaluate JS, take screenshots
- 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.
What ships with it
8 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.
- scripts/browser-console.js 5.8 KB runs code
- scripts/browser-cookies.js 861 B runs code
- scripts/browser-eval.js 1.5 KB runs code
- scripts/browser-nav.js 1.8 KB runs code
- scripts/browser-pick.js 5.1 KB runs code
- scripts/browser-screenshot.js 832 B runs code
- scripts/browser-start.js 2.1 KB runs code
- scripts/package.json 239 B
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.
- 10d ago First seen · 174 lines · 60 tokens per session scan A 38162166b1bd
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.
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…
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…
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.
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.
agent-browser
Headless browser automation CLI optimized for AI agents with accessibility tree snapshots and ref-based element selection.
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…