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 Microck/ordinary-claude-skills --skill chrome-devtoolsgit clone --depth 1 https://github.com/Microck/ordinary-claude-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/microck/ordinary-claude-skills/chrome-devtools)<a href="https://agentmods.dev/skills/microck/ordinary-claude-skills/chrome-devtools"><img src="https://agentmods.dev/badge/skills/microck/ordinary-claude-skills/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/microck/ordinary-claude-skills/chrome-devtools"><img src="https://agentmods.dev/badge/skills/microck/ordinary-claude-skills/chrome-devtools.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.02581 |
| Opus 5 | $0.00023 | $0.01290 |
| Sonnet 5 | $0.00009 | $0.00516 |
| Haiku 4.5 | $0.00005 | $0.00258 |
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 9d 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 The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
What ships with it
1 file 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.
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.
- 9d ago First seen · 361 lines · 45 tokens per session scan B 893563ea6ee5
chrome-devtools is a skill published in the GitHub repository Microck/ordinary-claude-skills (394 stars, last pushed 5d ago), with no licence file. It adds 45 tokens to every session and 2,581 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
safari-mcp-workflow
Inspect a scoped live site in Safari through Safari Technology Preview's local MCP server. Use for Safari-specific DOM, console, network, screenshot, accessibility, performance, interaction, responsive, or print-media evidence.
chrome-devtools-axi
Use the chrome-devtools-axi CLI to operate Chrome or investigate live page behavior. Default for ad hoc browsing, forms, rendered extraction, screenshots, DOM/CSS, console/network failures, responsive behavior, and performance or memory questions. Excludes static-only fetching, direct-MCP-only requests, explicitly…
browser-testing-with-devtools
Verify web apps with browser DevTools—DOM, console, network, performance, and accessibility at runtime. Use with Chrome DevTools MCP or headless browser tools.
browser-trace
Capture a full DevTools-protocol trace of a locally driven 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 local session, or feed…
remove-deadcode
Remove unused code from this project with ultrawork mode, LSP-verified safety, atomic commits. Triggers: remove dead code, dead code, cleanup, remove unused.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.