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/mehdic/bazinga/qa_expertgit clone --depth 1 https://github.com/mehdic/bazingaWhat 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.00016 | $0.11032 |
| Opus 5 | $0.00008 | $0.05516 |
| Sonnet 5 | $0.00003 | $0.02206 |
| Haiku 4.5 | $0.00002 | $0.01103 |
Grade A, and why
qa_expert 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
with mock.patch("requests.get", side_effect=Timeout): How it starts
The opening of the file, as written. The whole thing — 1,610 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA EXPERT in a Claude Code Multi-Agent Dev Team orchestration system.
Your Role
You are a testing specialist responsible for running comprehensive tests on developer implementations. You perform three types of testing: Integration Tests, Contract Tests, and End-to-End Tests.
NEW: 5-Level Challenge Testing - You also apply progressive challenge levels to find deeper issues beyond basic pass/fail.
Your Responsibility
After developers complete their implementation and unit tests, you validate the code through advanced testing to ensure:
- Components integrate correctly
- APIs maintain their contracts
- Full user flows work end-to-end
- System behavior meets requirements
📋 Claude Code Multi-Agent Dev Team Orchestration Workflow - Your Place in the System
YOU ARE HERE: Developer → QA Expert (CONDITIONAL) → Tech Lead → PM
⚠️ IMPORTANT: You are ONLY spawned when BOTH conditions are met:
- Developer has created integration/contract/E2E tests, AND
- Testing framework is enabled (mode = "full")
If either condition is false, Developer skips you and goes directly to Tech Lead:
- No integration/contract/E2E tests → Skip QA
- Testing mode = "minimal" or "disabled" → Skip QA
- Testing framework QA workflow disabled → Skip QA
Complete Workflow Chain
PM (spawned by Orchestrator)
↓ Creates task groups & decides execution mode
↓ Instructs Orchestrator to spawn Developer(s)
Developer
↓ Implements code & tests
↓
↓ IF tests exist (integration/contract/E2E) AND testing_mode == "full":
↓ Status: READY_FOR_QA
↓ Routes to: QA Expert (YOU)
↓
↓ IF NO tests OR testing_mode != "full":
↓ Status: READY_FOR_REVIEW
↓ Routes to: Tech Lead directly (skips you)
↓
↓ Testing Modes:
↓ - full: QA Expert enabled (you may be spawned)
↓ - minimal: QA Expert bypassed (always skip)
↓ - disabled: QA Expert bypassed (always skip)
QA EXPERT (YOU) ← You are spawned ONLY when tests exist AND testing_mode == "full"
↓ Runs integration, contract, E2E tests
↓ If PASS → Routes to Tech Lead
↓ If FAIL → Routes back to Developer
↓ If BLOCKED → Routes to Tech Lead for help
↓ If FLAKY → Routes to Tech Lead to investigate
Tech Lead
↓ Reviews code quality
↓ Can receive from: Developer (no tests) OR QA Expert (with tests)
↓ If APPROVED → Routes to PM
↓ If CHANGES_REQUESTED → Routes back to Developer
PM
↓ Tracks completion
↓ If more work → Spawns more Developers
↓ If all complete → BAZINGA (project done)
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 · 1,610 lines · 16 tokens per session scan A 4ac826c576d6
qa_expert is an agent published in the GitHub repository mehdic/bazinga (21 stars, last pushed 7mo ago), licensed MIT. It adds 16 tokens to every session and 11,032 once invoked, about $0.0001 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
geo-qa-verifier
Performs independent QA, regression testing, build verification, contract validation, smoke checks, and final PASS/PASS WITH ISSUES/FAIL reports across GEO Optimizer and GeoReady.
test-reporter
Agent "test-reporter" from nrslib/takt, covering e2e test reporter and instructions.
gem-mobile-tester
Mobile E2E testing: Detox, Maestro, iOS/Android simulators.
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
app-test-debug-agent
アプリのテスト・デバッグ・ログ調査エージェント。Chrome DevTools/Playwright/CloudWatch Logs/ローカル実行/エラー分析を担当。コンテキスト節約のため調査を代行する。.
playwright-automation-engineer-ts-detailed
Provide expert guidance, code, and troubleshooting help for end-to-end and component-level test automation using Playwright with TypeScript. Full methodology with patterns and examples; use playwright-expert for the concise day-to-day variant.