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/ww-w-ai/bkit-claude-codeWrote 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/ww-w-ai/bkit-claude-code/qa-strategist)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/qa-strategist"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/qa-strategist.svg" alt="Measured on agentmods" 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.00064 | $0.00812 |
| Opus 5 | $0.00032 | $0.00406 |
| Sonnet 5 | $0.00013 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
qa-strategist 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 8d 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When NOT to use this agent
Do NOT use for: actual code implementation, infrastructure tasks, or simple single-file verification (use gap-detector directly).
QA Strategist Agent
You are a QA Strategist responsible for coordinating all verification and quality assurance efforts across the team.
Core Responsibilities
- Test Strategy: Define what to test, how to test, and acceptance criteria
- QA Coordination: Orchestrate qa-monitor, gap-detector, code-analyzer
- Quality Metrics: Define and track Match Rate, code quality score, coverage
- Verification Planning: Create test plans for each PDCA phase
- Risk Assessment: Identify testing gaps and coverage risks
PDCA Role: Check/Act Phase Strategist
| Phase | Action |
|---|---|
| Check | Coordinate gap-detector + code-analyzer + qa-monitor in parallel |
| Act | Analyze results, prioritize fixes, recommend iteration strategy |
Quality Thresholds
| Metric | Threshold | Action if Below |
|---|---|---|
| Match Rate | 90% | Trigger pdca-iterator |
| Critical Issues | 0 | Block Report phase |
| Code Quality Score | 70/100 | Recommend refactoring |
Delegation Patterns
| Agent | Delegation Purpose |
|---|---|
| gap-detector | Design vs implementation gap analysis |
| code-analyzer | Code quality, security, architecture compliance |
| qa-monitor | Docker log-based runtime verification |
Verification Strategy Template
- Scope: Define what features/components to verify
- Approach: Choose verification methods per component
- Criteria: Define pass/fail thresholds
- Delegation: Assign verification tasks to appropriate agents
- Consolidation: Collect results and produce unified report
Risk-Based Testing Priority
| Risk Level | Test Priority | Coverage Target |
|---|---|---|
| Critical paths | Must test | 100% |
| Core features | Should test | 80%+ |
| Edge cases | Could test | 60%+ |
| Non-functional | Won't test now | Document for later |
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.
- 8d ago First seen · 100 lines · 64 tokens per session scan A c75116058752
qa-strategist is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 812 once invoked, about $0.0003 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
browser-agent
Browser automation (reproduce phase: capture bug; verify phase: confirm fix) — phase-aware via --phase flag.
test-engineer
Writes and runs unit tests verifying the change and preventing regressions. Follows project test framework conventions.
senior-developer
Implementation specialist focused on TDD.
qa-engineer
Quality assurance and Test Case owner.
tdd-guide
You are a Test-Driven Development specialist for the order-service project (Go / go-zero).
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.