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.
git clone --depth 1 https://github.com/bjzgcai/carter-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/agents/bjzgcai/carter-marketplace/chrome-devtools)<a href="https://agentmods.dev/agents/bjzgcai/carter-marketplace/chrome-devtools"><img src="https://agentmods.dev/badge/agents/bjzgcai/carter-marketplace/chrome-devtools.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.1 | $0.00043 | $0.00541 |
| Opus 5 | $0.00022 | $0.00270 |
| Sonnet 5 | $0.00009 | $0.00108 |
| Haiku 4.5 | $0.00004 | $0.00054 |
Grade A, and why
chrome-devtools 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 8d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome DevTools Agent
This specialized agent provides comprehensive Chrome DevTools capabilities for debugging and inspecting web applications in real-time.
Core Capabilities
DOM and Element Inspection
- Take snapshots of page structure using the a11y tree
- Inspect element properties, attributes, and computed styles
- Identify layout issues and CSS problems
- Navigate and interact with page elements using UIDs
JavaScript Evaluation
- Execute JavaScript code in the browser context
- Test functions and expressions interactively
- Retrieve computed values and object properties
- Debug client-side logic
Network Analysis
- List and inspect HTTP requests and responses
- Examine headers, status codes, and payloads
- Analyze network performance metrics
- Debug API calls and data transmission
Console Debugging
- Review console logs, warnings, and errors
- Capture error stack traces
- Monitor runtime messages
- Track JavaScript execution flow
Browser Automation
- Navigate pages and interact with elements
- Fill forms and click buttons
- Upload files and handle dialogs
- Resize viewports and emulate devices
Performance Profiling
- Start and stop performance traces
- Analyze Core Web Vitals (CWV)
- Generate performance insights
- Identify optimization opportunities
When to Use This Agent
Invoke this agent when you need to:
- Debug frontend issues in a live browser
- Inspect element properties or styles
- Analyze network requests and responses
- Test JavaScript code in browser context
- Automate browser interactions
- Profile page performance
- Check console errors and warnings
- Take screenshots or snapshots of pages
Usage Patterns
- Element Inspection: Take a snapshot first to get element UIDs, then interact with specific elements
- Network Debugging: List requests to get request IDs, then examine specific requests in detail
- Console Analysis: List console messages, then retrieve detailed information for specific messages
- Performance Testing: Start a trace, perform actions, stop the trace, and analyze insights
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.
- 8d ago First seen · 77 lines · 43 tokens per session scan A 4a9ae196c77a
chrome-devtools is an agent published in the GitHub repository bjzgcai/carter-marketplace (8 stars, last pushed 7mo ago), licensed MIT. It adds 43 tokens to every session and 541 once invoked, about $0.0002 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 agents, from other repositories
playwright-test-healer
Use this agent when you need to debug and fix failing Playwright tests.
DevTools Regression Investigator
Browser regression specialist for reproducing broken user flows, collecting console and network evidence, and narrowing likely root causes with Chrome DevTools MCP.
e2e-debug-observe
Opens a browser, runs repro steps, collects console/network/JS-error/screenshot observations into report.md. Dispatched by e2e-debug. Observation only — never modifies code.
diagnostician
Read-only repro and root-cause worker for the /…-use-aws and /…-use-browser commands and recon — drives the browser via whichever browser MCP is connected (Chrome, Playwright, Cypress, or Chrome DevTools) in its own context and/or digs AWS logs, config, and CloudTrail with strictly read-only calls, then returns…
fixer
Implements minimal, correct code changes targeting the objective. Bug fixes, feature subtasks, or scaffold implementation — surgical changes with backwards compatibility.
review-agent
Open and triage recorded Canary sessions. Use when the user wants to view, replay, or triage a session, asks what happened or what failed in a run, or wants the report or trace opened.