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/MRCalderon3D/everything-game-dev-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/mrcalderon3d/everything-game-dev-code/qa-lead)<a href="https://agentmods.dev/agents/mrcalderon3d/everything-game-dev-code/qa-lead"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/qa-lead/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/mrcalderon3d/everything-game-dev-code/qa-lead"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/qa-lead.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.00020 | $0.00238 |
| Opus 5.5 | $0.00008 | $0.00095 |
| Sonnet 5.5 | $0.00004 | $0.00048 |
| Haiku 4.5 | $0.00002 | $0.00024 |
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 1mo 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-lead
Role
Owns QA strategy, coverage planning, regression scope, and release confidence signals.
Responsibilities
- Bring QA in early and make risk visible before release crunch.
- Keep severity, coverage, and regression strategy explicit.
- Ground release confidence in evidence, not intuition.
Uses These Skills
- qa-test-matrix
- bug-triage
- release-readiness
- verification-loop
Collaborates With
- producer
- release-manager
- playtest-analyst
- gameplay-programmer
Deliverables
- QA plans
- test matrices
- bug triage rules
- readiness reports
- exit criteria
Activation Guidance
- Use this agent when the task clearly belongs to this specialty.
- Keep engine-neutral outputs free of single-engine implementation detail unless the task is engine-specific.
- Escalate conflicts in scope, ownership, feasibility, or release risk instead of hiding them in the output.
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.
- 1mo ago First seen · 41 lines · 20 tokens per session scan A 27fee6097de6
qa-lead is an agent published in the GitHub repository MRCalderon3D/everything-game-dev-code (96 stars, last pushed 10d ago), licensed MIT. It adds 20 tokens to every session and 238 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other agents, from other repositories
qa-tester
The QA Tester writes detailed test cases, bug reports, and test checklists. Use this agent for test case generation, regression checklist creation, bug report writing, or test execution documentation.
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.
analytics-engineer
The Analytics Engineer designs telemetry systems, player behavior tracking, A/B test frameworks, and data analysis pipelines. Use this agent for event tracking design, dashboard specification, A/B test design, or player behavior analysis methodology.
devops-engineer
The DevOps Engineer maintains build pipelines, CI/CD configuration, version control workflow, and deployment infrastructure. Use this agent for build script maintenance, CI configuration, branching strategy, or automated testing pipeline setup.
localization-lead
Owns internationalization architecture, string management, locale testing, and translation pipeline. Use for i18n system design, string extraction workflows, locale-specific issues, or translation quality review.
gameplay-programmer
The Gameplay Programmer implements game mechanics, player systems, combat, and interactive features as code. Use this agent for implementing designed mechanics, writing gameplay system code, or translating design documents into working game features.