Borrowing it
Nothing to install: this file belongs to khalilbenaz/MDAN. 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/khalilbenaz/MDAN/main/.claude/commands/mdan-qa-test-design.mdgit clone --depth 1 https://github.com/khalilbenaz/MDANWrote 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/khalilbenaz/mdan/mdan-qa-test-design)<a href="https://agentmods.dev/commands/khalilbenaz/mdan/mdan-qa-test-design"><img src="https://agentmods.dev/badge/commands/khalilbenaz/mdan/mdan-qa-test-design/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/khalilbenaz/mdan/mdan-qa-test-design"><img src="https://agentmods.dev/badge/commands/khalilbenaz/mdan/mdan-qa-test-design.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.00071 | $0.00122 |
| Opus 5.5 | $0.00028 | $0.00049 |
| Sonnet 5.5 | $0.00014 | $0.00024 |
| Haiku 4.5 | $0.00007 | $0.00012 |
Grade A, and why
qa-test-design 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 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.
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
IT IS CRITICAL THAT YOU FOLLOW THIS COMMAND: LOAD the FULL @{project-root}/_mdan/qa/workflows/qa-test-design/wizard.md, READ its entire contents and follow its directions exactly!
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 · 7 lines · 71 tokens per session scan A 411aa34f8e9b
qa-test-design is a command published in the GitHub repository khalilbenaz/MDAN (0 stars, last pushed 12d ago), licensed MIT. It adds 71 tokens to every session and 122 once invoked, about $0.0003 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-24.
Other commands, from other repositories
verify
Grade work that already exists and decide whether it can merge. Runs the project's current unit, integration, and E2E suites plus security scanning and type checking, scores every dimension 0-10, and returns a merge verdict with a VERIFIED-vs-CLAIMED evidence manifest. Writes no test files and edits no source. Use…
cover
Generate tests that do not exist yet. Analyzes coverage gaps, then writes and runs new test files across three tiers (unit, integration via testcontainers, Playwright E2E), one test-generator agent per tier, healing failures for up to 3 iterations. Use when code has no tests or when raising coverage after…
add-test
Command "add-test" from go4cas/quiver, covering step 1 — determine test type, step 2 — write unit tests (vitest), step 3 — write e2e tests (playwright) and step 4 — run and fix.
test-suite
Run comprehensive test suite with coverage analysis.
verify
You are invoking the verify skill - comprehensive verification following Boris Cherny's pattern.
t00-playwright-test
A command for testing a locally running web app in a real browser with Playwright, a browser automation and testing tool. It checks normal user flows and selected edge cases, then reports results with screenshots.