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 ulises-jeremias/agent-toolkit --skill chrome-devtoolsgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/chrome-devtools)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/chrome-devtools"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/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/ulises-jeremias/agent-toolkit/chrome-devtools"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/chrome-devtools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 5 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 39 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 47 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 59 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 90 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Excessive Agency · line 113 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00050 | $0.02106 |
| Opus 5.5 | $0.00020 | $0.00842 |
| Sonnet 5.5 | $0.00010 | $0.00421 |
| Haiku 4.5 | $0.00005 | $0.00211 |
Grade A, and why
chrome-devtools scanned grade A 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
`list_network_requests` + `get_network_request` (HAR-like), `list_console_messages` with source-mapped stacks. Prefer over `curl` when JS rendering or auth is involved. How it starts
The opening of the file, as written. The whole thing — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Chrome DevTools
Control and inspect a live Chrome browser via the official ChromeDevTools/chrome-devtools-mcp (chrome-devtools-mcp, Apache-2.0) MCP server. Gives your coding agent the full power of Chrome DevTools for runtime debugging, network inspection, performance analysis, and rendering diagnostics — while playwright-cli remains the primary tool for deterministic interaction and E2E validation.
Complementarity:
playwright-cli→ deterministiclocator/snapshot/assertworkflows, multi-tab, traces, screenshots.chrome-devtools→ network + console + performance traces + rendering diagnostics + Puppeteer-based reliable automation via DevTools. Do not re-implement Playwright flows via DevTools JSON-RPC; pick the right provider per capability (see decision table).
When to use which provider
| Need | Use playwright-cli |
Use chrome-devtools |
Either |
|---|---|---|---|
| Click / fill / navigate deterministically | ✅ locators, snapshot → stable eN refs, fixtures |
— | |
| Take screenshot of rendered state (verification required before declaring UI good) | ✅ screenshot + trace |
✅ take_screenshot + rendering inspection |
✅ |
| Assert E2E condition / generate test | ✅ assertions, e2e-runner specs |
— | |
| Inspect DOM / accessibility tree / computed styles | snapshot (a11y-aware) limited |
✅ DOM, a11y tree, style inspection | |
| Network requests / console messages / runtime debugging | limited | ✅ list_network_requests, console, source-mapped stack traces |
|
| Performance trace / CrUX field data / insights | — | ✅ performance_* tools + CrUX |
|
| Reliable automation that auto-waits | — | ✅ Puppeteer-based click/type/navigate via DevTools |
|
| Extract JS-rendered data quickly | ✅ snapshot + CLI loop |
Rule for design workflows: design-improvement and design-assessment use playwright-cli for implement → run → capture (primary capture + interaction); pull in chrome-devtools when browser.network / browser.console / browser.performance / browser.runtime-debug is required. Either MCP alone suffices for degraded mode; together they cover implement → render → capture → inspect → compare → iterate.
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 · 147 lines · 50 tokens per session scan A 81a9dbb9ba16
chrome-devtools is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 50 tokens to every session and 2,106 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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.
browser-trace
Capture a full DevTools-protocol trace of any browser automation — CDP firehose, screenshots, and DOM dumps — then bisect the stream into per-page searchable buckets. Use when the user wants to debug a failed run, audit network/console/DOM activity, attach a trace to an in-progress session, or feed structured per-page…
chatcrystal-debug-recall
Recall ChatCrystal memories for debugging tasks involving failing tests, compiler errors, runtime exceptions, dependency issues, environment breakage, or performance regressions. Use when historical root causes, fixes, or pitfalls may accelerate diagnosis before proposing a fix.
skillnote-doctor
A diagnostic tool for OpenClaw agents -- checks skill registry connectivity, AGENTS.md setup, config file validity, and installed skill health. Use when your setup seems broken, skills aren't loading, or you want to audit your agent's configuration.
bisect
Use when hunting a regression, phrases like "bisect", "find the commit that broke X", "this used to work", "regression in test Y", "when did start". Also use when escalated from ci-debug-loop because log analysis can't pinpoint the offending change, or when a previously-passing test/build/behavior is now failing and…
review-performance
Use when the user explicitly asks for a performance review, benchmark review, profiling review, perf audit, pprof analysis, allocation review, latency regression check, hot-path review, throughput review, "is this fast enough", or "review perf". This skill is opt-in only — never run automatically as part of review-all…