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 ihatesea69/kiro-kit --skill chrome-devtoolsgit clone --depth 1 https://github.com/ihatesea69/kiro-kitWrote 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/ihatesea69/kiro-kit/chrome-devtools)<a href="https://agentmods.dev/skills/ihatesea69/kiro-kit/chrome-devtools"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/chrome-devtools/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/ihatesea69/kiro-kit/chrome-devtools"><img src="https://agentmods.dev/badge/skills/ihatesea69/kiro-kit/chrome-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00034 | $0.00267 |
| Opus 5.5 | $0.00014 | $0.00107 |
| Sonnet 5.5 | $0.00007 | $0.00053 |
| Haiku 4.5 | $0.00003 | $0.00027 |
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 1mo 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
Chrome DevTools
Activate this skill when automating browsers, testing web interfaces, or capturing screenshots.
When to Use
- Testing API documentation UIs
- Capturing screenshots of admin panels
- Automating form submissions for testing
- Debugging web-based monitoring dashboards
- Scraping data from web interfaces
Puppeteer Usage
const browser = await puppeteer.launch();
const page = await browser.newPage();
await page.goto('http://localhost:3000');
await page.screenshot({ path: 'screenshot.png' });
await browser.close();
Common Operations
- Navigate to URLs and wait for network idle
- Fill forms and click buttons
- Take full-page or element screenshots
- Extract text content from pages
- Monitor network requests and responses
- Execute JavaScript in page context
Rules
- Always close browser instances after use
- Set appropriate timeouts for page loads
- Use headless mode for CI environments
- Handle navigation errors gracefully
- Respect rate limits when scraping
What ships with it
20 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.
- 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/.gitignore 12 B
- 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.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.
- 1mo ago First seen · 48 lines · 34 tokens per session scan A d139cd596220
chrome-devtools is a skill published in the GitHub repository ihatesea69/kiro-kit (19 stars, last pushed 2mo ago), licensed MIT. It adds 34 tokens to every session and 267 once invoked, about $0.0001 per session on Opus 5.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-30.
Other skills, from other repositories
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
surf
Control Chrome browser via CLI for testing, automation, and debugging. Use when the user needs browser automation, screenshots, form filling, page inspection, network/CPU emulation, DevTools streaming, or AI queries via ChatGPT/Gemini/Perplexity/Grok/AI Studio.
tauri-mcp-cli
Use the Tauri MCP CLI to start and recover driver sessions, automate Tauri webviews, capture UI state, debug IPC, and work with mobile or remote devices. Use whenever an agent needs to operate a Tauri v2 app from terminal commands.
acrawl-mcp
Drive the acrawl MCP server for browser automation, web scraping, and live DevTools inspection — navigating pages, clicking, filling forms, extracting structured data, and auditing network traffic, console errors, cookies, storage, performance, accessibility, and code coverage. Use this whenever a task touches acrawl…
use-peek
Use the peek CLI to inspect, debug, and interact with native macOS app windows. Use when the user asks to debug a macOS app, inspect UI elements, take screenshots, click buttons, or automate interactions with native apps.
debug-failed-action
When your last vsact returned an unexpected result (NOTFOUND, no visible state change, suspected silent failure), run this skill with the action's pre-token. Pulls console errors, network failures, and current performance into one report.