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 skills add MRCalderon3D/everything-game-dev-code --skill qa-test-matrixgit 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/skills/mrcalderon3d/everything-game-dev-code/qa-test-matrix)<a href="https://agentmods.dev/skills/mrcalderon3d/everything-game-dev-code/qa-test-matrix"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/qa-test-matrix/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/skills/mrcalderon3d/everything-game-dev-code/qa-test-matrix"><img src="https://agentmods.dev/badge/skills/mrcalderon3d/everything-game-dev-code/qa-test-matrix.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.00027 | $0.00407 |
| Opus 5.5 | $0.00011 | $0.00163 |
| Sonnet 5.5 | $0.00005 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
qa-test-matrix 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 10d 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 Test Matrix
Purpose
Build a coverage matrix that shows what must be tested, on which configurations, and at what milestone confidence level.
Use When
- a milestone or release is approaching
- test scope is unclear
- platform and feature combinations are multiplying
Inputs
- feature list
- platform list
- risk areas
- release gates
Process
- map features to platforms, states, and risk classes
- define must-pass versus nice-to-have coverage
- highlight unsupported or unowned combinations
- link each coverage area to owners and evidence sources
- update the matrix as scope changes
Outputs
- QA test matrix
- coverage gaps
- ownership map
- test-pass priorities
Quality Bar
- every shipped feature is covered with at least its happy path, key edge cases, and failure handling
- each test case states preconditions, steps, and an observable expected result
- coverage is traceable: every GDD acceptance criterion maps to at least one test case
- platform and device variations appear as explicit matrix axes, not assumptions
Common Failure Modes
- test cases written from implementation knowledge instead of player-facing behavior
- matrices that grow stale as features change, testing what no longer exists
- edge cases and failure paths omitted because the happy path passes
- no traceability, so removed features leave orphan tests and new ones ship untested
Related Agents
- qa-lead
- release-manager
- producer
Related Commands
- qa-plan
- release-check
- verify
Notes
- Keep this skill aligned with the relevant rules layer and current project documentation.
- If engine-specific constraints materially change the workflow, hand off to the matching engine skill or engine-specific reviewer.
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.
- 10d ago First seen · 62 lines · 27 tokens per session scan A ece73bf1508b
qa-test-matrix is a skill published in the GitHub repository MRCalderon3D/everything-game-dev-code (96 stars, last pushed 11d ago), licensed MIT. It adds 27 tokens to every session and 407 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-10-10.
Other skills, from other repositories
smoke-check
Run the critical path smoke test gate before QA hand-off. Executes the automated test suite, verifies core functionality, and produces a PASS/FAIL report. Run after a sprint's stories are implemented and before manual QA begins. A failed smoke check means the build is not ready for QA.
qa-plan
Generate a QA test plan for a sprint or feature. Reads GDDs and story files, classifies stories by test type (Logic/Integration/Visual/UI), and produces a structured test plan covering automated tests required, manual test cases, smoke test scope, and playtest sign-off requirements. Run before sprint begins or when…
automated-smoke-test
Run an automated smoke test using the godot-mcp server. Launches the project, captures debug output, and checks for errors or crashes.
cgs-vertical-slice
Use for vertical slice tasks that validate whether a full game loop can be built at representative quality before production commitment; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-adopt
Use for adopt tasks that inventory existing source, assets, docs, and tests before mapping work into CGS structure; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-architecture-review
Use for architecture review tasks that review architecture for layer violations, scalability risks, engine misuse, testing seams, and production readiness; produce verification evidence, changed or proposed files, and handoff boundaries.