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.
/plugin marketplace add lttr/claude-marketplacenpx agentmods add plugins/lttr/claude-marketplace/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/plugins/lttr/claude-marketplace/browser-tools)<a href="https://agentmods.dev/plugins/lttr/claude-marketplace/browser-tools"><img src="https://agentmods.dev/badge/plugins/lttr/claude-marketplace/browser-tools.svg" alt="Measured on agentmods" height="20"></a>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 3d 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.
What it actually says
{
"name": "browser-tools",
"description": "Chrome automation tools for agent-assisted web testing and interaction using Chrome DevTools Protocol",
"version": "1.6.1",
"author": {
"name": "Lukas Trumm"
}
}
What it installs
The manifest is a name and a version. 1 skill, 1 command travel with it, and installing the plugin installs all of them — 60 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 3d ago First seen · 9 lines scan A 67e51337902d
browser-tools is a plugin published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed 6d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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 plugins, from other repositories
e2e-harness
Playwright E2E test-harness engineering — wraps Playwright's official AI test agents (npx playwright init-agents --loop=claude generates planner/generator/healer). Three skills close the planner -> generator -> healer self-improving loop: e2e-setup onboards the full harness (agents, auth separation via storageState +…
agent-browser
Automates browser interactions for web testing, form filling, screenshots, and data extraction.
agentcursor
Local, free, human-like browser automation over MCP. A visible, realistic cursor for coding agents, E2E testing, and workflows on real sites.
e2e-runner
JSON-driven E2E browser test runner — no JavaScript test files needed. Parallel execution against a Chrome pool (browserless, CDP, Lightpanda, Obscura, Steel), 28+ built-in actions, visual verification, network debugging, flaky test detection, reusable modules, and a real-time dashboard. Includes 3 specialized agents.
mockhunter
Audit live web pages for fake/mock data — 5-phase Playwright + Claude Code skill that classifies every visible value as REAL, MOCK, LLM, HARDCODED, BROKEN, or UNKNOWN.
chrome-ui-test
Tests automatisés d'interface utilisateur dans Chrome : navigation, validation visuelle, tests fonctionnels et responsive.