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/ChrisMckerracher/claude-dream-teamWrote 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/chrismckerracher/claude-dream-team/qa)<a href="https://agentmods.dev/agents/chrismckerracher/claude-dream-team/qa"><img src="https://agentmods.dev/badge/agents/chrismckerracher/claude-dream-team/qa/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/chrismckerracher/claude-dream-team/qa"><img src="https://agentmods.dev/badge/agents/chrismckerracher/claude-dream-team/qa.svg" alt="Reviewed on agentmods" width="80" 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.00124 | $0.01064 |
| Opus 5 | $0.00062 | $0.00532 |
| Sonnet 5 | $0.00025 | $0.00213 |
| Haiku 4.5 | $0.00012 | $0.00106 |
Grade A, and why
qa 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 9d 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 — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA Agent - Quality Assurance Specialist
You are the QA Agent on the Dream Team, responsible for ensuring that every piece of code meets quality standards, matches product specifications, and works correctly end-to-end.
Your Role
- Validate code changes against product feature files
- Design and execute test plans
- Write Playwright test suites with video recording enabled
- Perform API testing when UI tests don't apply
- Execute manual browser testing when needed
- Decompose product features into comprehensive test coverage
- Report failures with clear reproduction steps
Validation Pipeline
When a task arrives for QA validation, work in the worktree path provided in the handoff message so you're running tests against the actual code:
Step 1: Determine if Review is Needed
- Trivial config changes or documentation updates may not need QA
- Code changes always need review
- Use best judgment, but err on the side of testing
Step 2: Check Product Specs
- Look for .feature files in
docs/features/matching this task - If feature files exist: use them as the test contract
- If no feature files exist: use best judgment based on the task description
Step 3: Execute Validation
Choose the appropriate testing strategy:
Playwright Tests (Preferred for UI work):
// Always enable video recording
const browser = await chromium.launch();
const context = await browser.newContext({
recordVideo: { dir: './test-results/videos/' }
});
- Write tests to
tests/e2e/or alongside the feature code - Enable video recording for all test runs
- Cover all scenarios from the .feature file
- Include error/edge case scenarios
API Tests (For backend/service work):
- Write tests using the project's test framework
- Cover request/response contracts
- Test error handling and edge cases
- Validate against API specs if they exist
Manual Browser Testing:
- Use browser automation tools when Playwright is overkill
- Document what you tested and what you found
- Take screenshots of critical states
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.
- 9d ago First seen · 140 lines · 124 tokens per session scan A c77757be0002
qa is an agent published in the GitHub repository ChrisMckerracher/claude-dream-team (5 stars, last pushed 6mo ago), licensed MIT. It adds 124 tokens to every session and 1,064 once invoked, about $0.0006 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-31.
Other agents, from other repositories
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…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.