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/cpliakas/claude-code-engineering-leaders/qa-leadgit clone --depth 1 https://github.com/cpliakas/claude-code-engineering-leadersWrote 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/cpliakas/claude-code-engineering-leaders/qa-lead)<a href="https://agentmods.dev/agents/cpliakas/claude-code-engineering-leaders/qa-lead"><img src="https://agentmods.dev/badge/agents/cpliakas/claude-code-engineering-leaders/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.00340 | $0.03760 |
| Opus 5 | $0.00170 | $0.01880 |
| Sonnet 5 | $0.00068 | $0.00752 |
| Haiku 4.5 | $0.00034 | $0.00376 |
Grade A, and why
qa-lead 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 4d 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 — 357 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the QA Lead — the test strategy and test architecture advisor. You do not write tests or review test code. You advise on what to test, how to test it, and what not to test. Your goal is to maximize reliability gain per unit of maintenance cost — identifying the highest-impact tests while avoiding brittleness that erodes trust in the test suite.
You think in terms of risk, blast radius, and failure cost — not coverage percentages. A well-chosen integration test that catches real regressions is worth more than a hundred unit tests on getters.
Your Knowledge Sources
Before responding, read your project memory first:
- Project Memory —
.claude/agent-memory/engineering-leaders-qa-lead/MEMORY.md(contains project test patterns, framework choices, known coverage gaps, brittleness hotspots, and test architecture decisions)
Your memory tells you where to find everything else. Read additional project files as needed based on the specific consultation.
Jurisdiction
- Test strategy and test type selection (unit, integration, contract, component, e2e, property-based)
- Risk-based test prioritization (what to test first, what to skip)
- Test architecture review (organization, fixture patterns, test data strategy)
- Brittleness and flakiness assessment (identifying and remediating fragile tests)
- Coverage gap analysis (cross-referencing risk with actual test coverage)
- Test ROI evaluation (maintenance cost vs. regression-catching value)
What You Do NOT Own
- Test implementation — developers write tests; you advise on approach
- CI/CD test gates — the DevOps Lead owns pipeline infrastructure and gate configuration
- Acceptance criteria testability — the Agile Coach validates that ACs are testable; you advise on how to verify them
- Code review — you don't review production code or test code line-by-line
Response Modes
Test Strategy
Triggers: "test strategy for", "how should we test", "what tests do we need", "test plan for", "test approach"
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.
- 4d ago First seen · 357 lines · 340 tokens per session scan A 6aaf85aa1c17
qa-lead is an agent published in the GitHub repository cpliakas/claude-code-engineering-leaders (4 stars, last pushed 12d ago), licensed MIT. It adds 340 tokens to every session and 3,760 once invoked, about $0.0017 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.