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/buzzmatic/awesome-agent-skills/chrome-devtoolsnpx skills add Buzzmatic/awesome-agent-skills --skill chrome-devtoolsgit clone --depth 1 https://github.com/Buzzmatic/awesome-agent-skillsWrote 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/buzzmatic/awesome-agent-skills/chrome-devtools)<a href="https://agentmods.dev/skills/buzzmatic/awesome-agent-skills/chrome-devtools"><img src="https://agentmods.dev/badge/skills/buzzmatic/awesome-agent-skills/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 | $0.00045 | $0.02562 |
| Opus 5 | $0.00023 | $0.01281 |
| Sonnet 5 | $0.00009 | $0.00512 |
| Haiku 4.5 | $0.00005 | $0.00256 |
Grade B, and why
chrome-devtools scanned grade B with 1 finding 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 4d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo apt-get install imagemagick This is a copy
88% identical to chrome-devtools — 50 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 361 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome DevTools Agent Skill
Browser automation via executable Puppeteer scripts. All scripts output JSON for easy parsing.
Quick Start
CRITICAL: Always check pwd before running scripts.
Installation
Step 1: Install System Dependencies (Linux/WSL only)
On Linux/WSL, Chrome requires system libraries. Install them first:
pwd # Should show current working directory
cd skills/chrome-devtools/scripts
./install-deps.sh # Auto-detects OS and installs required libs
Supports: Ubuntu, Debian, Fedora, RHEL, CentOS, Arch, Manjaro
macOS/Windows: Skip this step (dependencies bundled with Chrome)
Step 2: Install Node Dependencies
npm install # Installs puppeteer, debug, yargs
Step 3: Install ImageMagick (Optional, Recommended)
ImageMagick enables automatic screenshot compression to keep files under 5MB:
macOS:
brew install imagemagick
Ubuntu/Debian/WSL:
sudo apt-get install imagemagick
Verify:
magick -version # or: convert -version
Without ImageMagick, screenshots >5MB will not be compressed (may fail to load in Gemini/Claude).
Test
node navigate.js --url https://example.com
# Output: {"success": true, "url": "https://example.com", "title": "Example Domain"}
Available Scripts
All scripts are in skills/chrome-devtools/scripts/
CRITICAL: Always check pwd before running scripts.
Script Usage
./scripts/README.md
Core Automation
navigate.js- Navigate to URLsscreenshot.js- Capture screenshots (full page or element)click.js- Click elementsfill.js- Fill form fieldsevaluate.js- Execute JavaScript in page context
Analysis & Monitoring
snapshot.js- Extract interactive elements with metadataconsole.js- Monitor console messages/errorsnetwork.js- Track HTTP requests/responsesperformance.js- Measure Core Web Vitals + record traces
Usage Patterns
Single Command
pwd # Should show current working directory
cd skills/chrome-devtools/scripts
node screenshot.js --url https://example.com --output ./output/page.png
Important: Save screenshots to a known output directory (e.g. ./output/).
What ships with it
21 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.
- favicon/icon.png 1.3 KB
- references/cdp-domains.md 17 KB
- references/performance-guide.md 21 KB
- references/puppeteer-reference.md 19 KB
- scripts/__tests__/selector.test.js 6.4 KB runs code
- scripts/click.js 2.2 KB runs code
- scripts/console.js 1.7 KB runs code
- scripts/evaluate.js 1.1 KB runs code
- scripts/fill.js 1.9 KB runs code
- scripts/install-deps.sh 4.3 KB runs code
- scripts/install.sh 2.1 KB runs code
- scripts/lib/browser.js 2.4 KB runs code
- scripts/lib/selector.js 5.3 KB runs code
- scripts/navigate.js 994 B runs code
- scripts/network.js 2.7 KB runs code
- scripts/package-lock.json 40 KB
- scripts/package.json 321 B
- scripts/performance.js 3.8 KB runs code
- scripts/README.md 5.2 KB
- scripts/screenshot.js 5.9 KB runs code
- scripts/snapshot.js 3.4 KB runs code
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.
- 4d ago First seen · 361 lines · 45 tokens per session scan B 68a1cffcafcc
chrome-devtools is a skill published in the GitHub repository Buzzmatic/awesome-agent-skills (1 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 2,562 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). It is 88% identical to chrome-devtools, differing in 50 lines, and is treated as a copy.
Other skills, from other repositories
v8-jit
V8 JIT optimization patterns for writing high-performance JavaScript in Next.js server internals. Use when writing or reviewing hot-path code in app-render, stream-utils, routing, caching, or any per-request code path. Covers hidden classes / shapes, monomorphic call sites, inline caches, megamorphic deopt, closure…
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.