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/fmind/dot/chrome-devtoolsnpx skills add fmind/dot --skill chrome-devtoolsgit clone --depth 1 https://github.com/fmind/dotWrote 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/fmind/dot/chrome-devtools)<a href="https://agentmods.dev/skills/fmind/dot/chrome-devtools"><img src="https://agentmods.dev/badge/skills/fmind/dot/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.00038 | $0.00731 |
| Opus 5 | $0.00019 | $0.00365 |
| Sonnet 5 | $0.00008 | $0.00146 |
| Haiku 4.5 | $0.00004 | $0.00073 |
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 yesterday.
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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome DevTools
Chrome DevTools for agents connects AI coding agents to a live Chrome browser via the Model Context Protocol (MCP) or CLI. It enables automated browser inspection, performance tracing (Core Web Vitals, LCP), accessibility tree evaluation, cookie analysis, network inspection, and memory leak diagnosis. End-to-end browser journeys route through playwright; modern web standards and native patterns route through modern-web.
1. Configure MCP Server
Add the chrome-devtools MCP server to the current agent harness using agent-mcp:
# Project-scoped MCP registration (Antigravity CLI example)
agy mcp add chrome-devtools -- npx -y chrome-devtools-mcp@latest
2. Debugging and Auditing Workflow
- Launch browser session: Start Chrome with remote debugging enabled, or allow the MCP server to launch and control an isolated browser instance via Puppeteer.
- Performance and LCP: Record traces to identify slow rendering phases, server response latency, render-blocking resources, and Largest Contentful Paint culprits.
- Accessibility tree audits: Inspect computed accessible names, ARIA roles, and color contrast ratios to ensure WCAG compliance alongside quality-assurance.
- Memory and cookies: Take heap snapshots to identify detached DOM nodes and memory leaks; verify
SameSite,Secure, andPartitionedcookie attributes.
Gotchas
- Sensitive data exposure: The MCP server grants full inspection and execution control over the browser session; avoid using personal profiles or sharing sensitive credentials.
- Headless versus headed: Automated testing runs headless by default; visual debugging and layout inspections may require headed mode.
- Complementary to Playwright: Use Playwright for deterministic functional and E2E regression tests; reserve Chrome DevTools MCP for deep runtime profiling, traces, and live diagnostics.
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.
- yesterday First seen · 51 lines · 38 tokens per session scan A 0c8d2dc9303d
chrome-devtools is a skill published in the GitHub repository fmind/dot (4 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 731 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-09-04.
Other skills, from other repositories
go-stack
Build Go projects, libraries, CLIs, TUIs, web apps, or ADK agents with the standard package layout and pinned tooling.
python-stack
Build typed Python projects with uv, Ruff, ty, pytest, Litestar, and Typer. Use for packages, CLIs, web apps, tests, typing, or API verification.
hugo
Canonical Hugo static-site stack with the Hextra docs theme — Hugo Modules, mise tasks, dprint, lefthook, and GitHub Pages deploy. Use for documentation sites, project docs, and static websites.
k8s-local
Create and manage local Kubernetes clusters (k3d or kind) and deploy to them with kubectl, helm, helmfile, and skaffold. Use for local k8s cluster setup, dev loops, and debugging.
release
Cut or verify a versioned release — bump semver, generate the changelog with git-cliff, tag and publish on GitHub, or reconcile an already-published tag and assets.
chezmoi
Manage chezmoi dotfiles: source naming, Go templates, age-encrypted secrets, and the edit-source then apply/diff workflow.