Borrowing it
Nothing to install: this file belongs to incubateur-ademe/benefriches. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/incubateur-ademe/benefriches/main/.claude/commands/adw-qa.mdgit clone --depth 1 https://github.com/incubateur-ademe/benefrichesWrote 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/commands/incubateur-ademe/benefriches/adw-qa)<a href="https://agentmods.dev/commands/incubateur-ademe/benefriches/adw-qa"><img src="https://agentmods.dev/badge/commands/incubateur-ademe/benefriches/adw-qa/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/commands/incubateur-ademe/benefriches/adw-qa"><img src="https://agentmods.dev/badge/commands/incubateur-ademe/benefriches/adw-qa.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.00020 | $0.00604 |
| Opus 5.5 | $0.00008 | $0.00242 |
| Sonnet 5.5 | $0.00004 | $0.00121 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
adw-qa 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 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.
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
Walk the Scenarios of the spec at $1 in a real browser against this worktree's e2e stack. Write qa.md in the spec's directory and the screenshots in a qa/ folder beside it. Change no file in the worktree: QA observes the app, it does not fix it.
If Scenarios is None, write qa.md saying so and return a pass.
- Read
.e2e-stackat the repository root: the app is atBASE_URL, the API atAPI_URL, the mail catcher atMAILCATCHER_URL, the database atDATABASE_URL. Use only these. If the file is missing or the app does not answer, stop and report an environment failure, not a QA verdict. - Drive the browser with the Playwright MCP tools. If they are missing, stop and say the session must be started with
--mcp-config adws/mcp/playwright.json. - Collect the design: images and PDFs in the
attachments/folder beside the spec. - Set up each scenario's starting state the way the e2e fixtures do (
apps/e2e-tests/AGENTS.md): a fresh user, sites and projects seeded through the API, the database only for what the API cannot do. Never seed the behaviour the scenario checks. - Walk each scenario as a user would, through the UI, then check its expected result on the page. Take at least one screenshot per scenario, at the expected result, and copy it to
qa/<n>-<slug>.png. - A scenario fails when its expected result does not hold, or when you cannot run it (setup impossible, step unclear). Record the steps, expected, observed and the screenshot. Never retry until it passes: a failure seen once is reported.
- Compare every screen that has a mockup with it, by eye. Differences (layout, wording, colour, a missing element) are observations, not failures, unless the scenario's expected result requires that element.
Write qa.md: the verdict, one section per scenario (steps, expected, observed, screenshot, pass or fail), then the observations against the mockups.
Pass only when no scenario failed. End your final message with the verdict, alone in a json code block:
{
"pass": false,
"failures": [
{
"scenario": "...",
"expected": "...",
"observed": "...",
"screenshot": "qa/1-....png"
}
],
"observations": [
{ "screen": "...", "mockup": "attachments/....png", "difference": "..." }
]
}
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 · 39 lines · 20 tokens per session scan A 81d65c9f19a9
adw-qa is a command published in the GitHub repository incubateur-ademe/benefriches (45 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 604 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-10-21.
Other commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
verify-pr
Verify a PR's frontend changes through browser automation.
monobrowse
Launch monomind browse for web UI testing and automation — native TypeScript CDP client, no external binary needed.