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 christopherlouet/claude-base --skill qa-chromegit clone --depth 1 https://github.com/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/qa-chrome)<a href="https://agentmods.dev/skills/christopherlouet/claude-base/qa-chrome"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/qa-chrome/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/christopherlouet/claude-base/qa-chrome"><img src="https://agentmods.dev/badge/skills/christopherlouet/claude-base/qa-chrome.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.00061 | $0.00705 |
| Opus 5.5 | $0.00024 | $0.00282 |
| Sonnet 5.5 | $0.00012 | $0.00141 |
| Haiku 4.5 | $0.00006 | $0.00071 |
Grade A, and why
qa-chrome 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 21d 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.
How it starts
The opening of the file, as written. The whole thing — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Visual Tests and Chrome Debugging (pointer)
DevTools features (network inspection, profiling, accessibility tree, console replay) are canonical at the Chrome team's ChromeDevTools/chrome-devtools-mcp (Apache-2.0). Since 2026 it ships seven skills next to its MCP server: chrome-devtools, chrome-devtools-cli, a11y-debugging, debug-optimize-lcp, memory-leak-debugging, cookie-debugging, troubleshooting.
# The plugin bundles the skills and the MCP server. The marketplace follows the vendor's default
# branch: what you get is the plugin.json there ([email protected] on 2026-10-04).
/plugin marketplace add ChromeDevTools/chrome-devtools-mcp
/plugin install chrome-devtools-mcp@chrome-devtools-plugins
# MCP server only, pinned by us (the vendor's docs show @latest)
claude mcp add chrome-devtools --scope user npx [email protected]
This skill scopes to the manual-review checklist when using Claude Code's --chrome flag — what to look for, not how the API works.
Prerequisites
- Claude Code launched with
--chrome - "Claude in Chrome" extension v1.0.36+
- Google Chrome open (not Brave/Arc/Firefox; no headless mode; WSL unsupported)
Manual-review checklist
When asked to visually validate a page or flow:
- Page loads with no console error
- Layout correct (no overflow, no overlap, no z-index bug)
- Text readable (contrast meets WCAG AA — see
wcag-audit) - Images loaded (no broken sources, lazy-load completes)
- Links functional (no 404 in network panel)
- Forms submittable (validation triggers on bad input)
- Responsive OK across mobile/tablet/desktop breakpoints — see
qa-design(responsive category) - No network error (no 4xx/5xx unless intentional)
Expected output
Structured report:
- Screenshots/GIFs of issues
- List of console + network errors with source location
- Recommendations sorted by severity
- Overall verdict:
OK/Warnings/Errors
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.
- 21d ago Changed · +7 lines 30dbb6d2bcd2
- 27d ago Changed · -2 lines 22a63493e716
- 28d ago Changed · -4 lines aa29bd1d8980
- 29d ago Changed · -1 lines 75383bd652a5
- 1mo ago First seen · 56 lines · 61 tokens per session scan A a70b1d2a3cff
qa-chrome is a skill published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 705 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
agent-e2e-test-specialist
Specialist subagent: Playwright, Cypress, and visual regression testing specialist. Use only when the user explicitly asks for E2E tests, browser test automation, or visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
e2e-testing-patterns
Master end-to-end testing with Playwright and Cypress to build reliable test suites that catch bugs, improve confidence, and enable fast deployment. Use when implementing E2E tests, debugging flaky tests, or establishing testing standards.
memstack-development-webapp-testing
Use when the user says 'write browser tests', 'test this page', 'playwright test', 'e2e test', 'end to end test', 'browser test', 'test the UI', or needs Playwright-based browser testing for a web application. Do NOT use for unit tests, API tests, or non-browser testing.
playwright
Playwright end-to-end testing best practices for web applications, covering test design, locator strategies, and assertion patterns.
playwright-cursor-rules
Expert guidance for Playwright end-to-end testing with TypeScript and JavaScript best practices.
qa-testing-playwright
Builds and debugs Playwright E2E suites. Use when authoring browser tests, fixing flakes, or hardening Playwright CI and locator strategy.