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.
git 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/agents/christopherlouet/claude-base/qa-chrome)<a href="https://agentmods.dev/agents/christopherlouet/claude-base/qa-chrome"><img src="https://agentmods.dev/badge/agents/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/agents/christopherlouet/claude-base/qa-chrome"><img src="https://agentmods.dev/badge/agents/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.00036 | $0.00258 |
| Opus 5.5 | $0.00014 | $0.00103 |
| Sonnet 5.5 | $0.00007 | $0.00052 |
| Haiku 4.5 | $0.00004 | $0.00026 |
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 24d 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
QA-CHROME Agent
Visual audit and browser testing. Prerequisites: claude --chrome + Chrome extension.
Workflow
- Open: Navigate to the target page
- Inspection: Console, network errors, layout
- Responsive: Mobile (375px), Tablet (768px), Desktop (1440px)
- Flow: Test the main interactions
- Capture: Screenshots of anomalies
- Report: Structured summary with severity and score /10
Limitations
- Chrome only, visible window required (not headless)
- JS dialogs block the flow, WSL not supported
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.
- 24d ago Changed · -1 lines 4531b1d197a5
- 25d ago Changed 744d06f3eca4
- 1mo ago First seen · 36 lines · 36 tokens per session scan A 69219d243cde
qa-chrome is an agent published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 2d ago), licensed MIT. It adds 36 tokens to every session and 258 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-31.
Other agents, from other repositories
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
visual-qa-subagent
Performs visual QA inspection using Playwright browser automation.
reproduction-checker
Checks whether a specific reported bug still reproduces on the live site and reports a verdict with evidence. Use during a Bug Shepherd triage run.
forge-visual-verifier
Perceptual gate for spec [visual] acceptance criteria. Drives Playwright MCP (navigate + takescreenshot + evaluate), compares the resulting image against a saved baseline via an LLM-vision step, and reports pass|fail|blocked per AC. Invoked after all task-level structural checks pass and before FORGECOMPLETE is…
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.