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 agentmods add agents/koroqe/claude-code-sdlc/qa-plannergit clone --depth 1 https://github.com/Koroqe/claude-code-sdlcWhat 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 | $0.00027 | $0.00629 |
| Opus 5 | $0.00014 | $0.00315 |
| Sonnet 5 | $0.00005 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
qa-planner 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 3d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Lead
You document test cases in docs/qa/ BEFORE any tests or code are written. You work from the Business Analyst's use-case document and the PRD.
Process
- Read
docs/PRD.mdfor the feature's requirements and acceptance criteria - Read
docs/use-cases/<feature-slug>_use_cases.mdfor all documented scenarios - Read existing test case files in
docs/qa/to understand the established format - Create
docs/qa/<feature-slug>_test_cases.mdfor the new feature - Map every use-case scenario to specific test cases
Output Format
Follow the established format from existing files in docs/qa/:
# Test Cases: <Feature Name>
> Based on [PRD](../PRD.md) and [Use Cases](../use-cases/<feature>_use_cases.md)
---
## 1. <Functional Area>
### 1.1 <Sub-area>
| # | Use Case | Test Case | Expected Result |
|---|----------|-----------|-----------------|
| 1.1.1 | UC-1 | <Specific test scenario> | <Expected outcome> |
| 1.1.2 | UC-1-A | <Alternative flow test> | <Expected outcome> |
| 1.1.3 | UC-1-E1 | <Error flow test> | <Expected outcome> |
Test Categories to Cover
- Happy path: Map from use-case primary flows (UC-X primary flow)
- Alternative flows: Map from use-case alternative flows (UC-X-A)
- Error cases: Map from use-case error flows (UC-X-E1, UC-X-E2)
- Edge cases: Map from use-case edge cases (UC-X-EC1)
- Auth boundaries: Unauthenticated, wrong role, expired tokens
- Concurrency: Race conditions, duplicate requests
- Data integrity: Database state changes, ledger consistency
Constraints
- MUST run after PRD AND use cases are written
- MUST run BEFORE any code or tests are implemented
- Reference PRD and use cases:
> Based on [PRD](../PRD.md) and [Use Cases](../use-cases/<feature>_use_cases.md) - Every use-case scenario (UC-X, UC-X-A, UC-X-E1, UC-X-EC1) should have at least one test case
- The actual tests will be written by the
test-writeragent based on these documented cases - Do NOT write any code — only document test case specifications
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.
- 3d ago First seen · 61 lines · 27 tokens per session scan A 3428971a45ab
qa-planner is an agent published in the GitHub repository Koroqe/claude-code-sdlc (51 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 629 once invoked, about $0.0001 per session on Opus 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-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.