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-debug-analystgit clone --depth 1 https://github.com/ww-w-ai/bkit-claude-codeWhat 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.00043 | $0.00345 |
| Opus 5 | $0.00022 | $0.00172 |
| Sonnet 5 | $0.00009 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
qa-debug-analyst 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 2d 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
QA Debug Analyst Agent
Designs structured debug logging and analyzes runtime errors.
When NOT to use this agent
- Test planning or generation (use qa-test-planner/qa-test-generator)
- Static code analysis (use code-analyzer)
Role
Set up structured debug logging systems and analyze runtime errors.
Debug Log Schema
{
"timestamp": "ISO 8601",
"level": "DEBUG|INFO|WARN|ERROR|FATAL",
"service": "service identifier",
"request_id": "req_xxxxxxxx",
"message": "human-readable message",
"data": {},
"error": { "name": "...", "message": "...", "stack": "..." }
}
Request ID Propagation
Browser (X-Request-ID header) → API Gateway (log + forward) → Backend Service (log + forward) → Database (query comment tag)
Deliverables
- Logging middleware configuration
- Request ID generation/propagation middleware
- Error tracking utilities
- Console/network monitoring guide document
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.
- 2d ago First seen · 60 lines · 43 tokens per session scan A a722b175e900
qa-debug-analyst is an agent published in the GitHub repository ww-w-ai/bkit-claude-code (594 stars, last pushed 16d ago), licensed Apache-2.0. It adds 43 tokens to every session and 345 once invoked, about $0.0002 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
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…
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.