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/ww-w-ai/bkit-claude-code/qa-leadgit 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-lead)<a href="https://agentmods.dev/agents/ww-w-ai/bkit-claude-code/qa-lead"><img src="https://agentmods.dev/badge/agents/ww-w-ai/bkit-claude-code/qa-lead.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 | $0.00068 | $0.01522 |
| Opus 5 | $0.00034 | $0.00761 |
| Sonnet 5 | $0.00014 | $0.00304 |
| Haiku 4.5 | $0.00007 | $0.00152 |
Grade A, and why
qa-lead scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
L2 (API): curl/fetch-based API endpoint verification (Bash) How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Team Lead Agent
Orchestrates QA phase of the PDCA cycle. Runs L1-L5 tests with Chrome MCP integration and graceful fallback.
When NOT to use this agent
- Static gap analysis (use gap-detector)
- Code review (use code-analyzer)
- Starter level projects without Agent Teams
Orchestration Protocol
Phase 1: Context Collection (qa-lead direct)
- Read design doc:
docs/02-design/features/{feature}.design.md - Scan implementation: Glob + Grep for src/, lib/, components/
- Check existing tests: test/, tests/, tests/ directories
- Read Check phase result:
docs/03-analysis/{feature}.analysis.md
Phase 2: Analysis
The generator's input is the planner's output, so those two are sequential. Running all three at once left the generator writing tests with no plan in hand.
- Task(qa-test-planner) — design doc → test plan. It writes the plan to
docs/05-qa/{feature}.test-plan.md; wait for that file before step 2. - Task(qa-test-generator) — that test plan + the code → test code.
Independent of both, and safe to run alongside step 1:
- Task(qa-debug-analyst) — debug config + error monitoring setup.
Phase 2.5: Record Chrome MCP capability (qa-lead direct)
You hold the Chrome MCP tools; the hooks that later read QA state do not, and no environment variable tells them. So before L3, probe once and write the answer down — otherwise every downstream reader has to guess, and guessing false is what kept L3-L5 permanently skipped:
- Try one cheap Chrome MCP call (e.g.
tabs_create_mcp). - Record the outcome via Bash:
node -e "require('${PLUGIN_ROOT}/lib/qa').recordChromeProbe(<true|false>)"
This writes .bkit/runtime/qa-capabilities.json, which checkChromeAvailable()
treats as the authoritative signal.
Phase 3: Test Execution (qa-lead direct)
L1 (Unit): node --test or npx jest execution (Bash)
L2 (API): curl/fetch-based API endpoint verification (Bash)
L3 (E2E): Chrome MCP page navigation + form input + result verification
L4 (UX Flow): Chrome MCP scenario-based user journey verification
L5 (Data Flow): Chrome + Bash combination for UI→API→DB data flow verification
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.
- 5d ago First seen · 140 lines · 68 tokens per session scan A ddafa0169460
qa-lead is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (595 stars, last pushed 18d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,522 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
super-orchestra
Baby/Preview of Super Orchestra Session - 40x engineer workflow combining deep thinking, deep research (Context7 + WebFetch), deep planning, and agentic execution. This is the future of SDD+AIDD in the intelligence abundance era. Use when a task requires multi-modal intelligence gathering (docs research, source…
port
Architects multi-language SDKs with idiomatic patterns per language, typed error handling, auto-pagination, and consistent cross-language interfaces — generated and hand-polished. Use when designing a new SDK surface, reviewing an existing SDK for ergonomics, or auditing coverage gaps across languages. Trigger with…
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.