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 dcc-mcp/dcc-mcp-godot --skill godot-testing-qagit clone --depth 1 https://github.com/dcc-mcp/dcc-mcp-godotWrote 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/dcc-mcp/dcc-mcp-godot/godot-testing-qa)<a href="https://agentmods.dev/skills/dcc-mcp/dcc-mcp-godot/godot-testing-qa"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-godot/godot-testing-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/skills/dcc-mcp/dcc-mcp-godot/godot-testing-qa"><img src="https://agentmods.dev/badge/skills/dcc-mcp/dcc-mcp-godot/godot-testing-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.00068 | $0.00453 |
| Opus 5.5 | $0.00027 | $0.00181 |
| Sonnet 5.5 | $0.00014 | $0.00091 |
| Haiku 4.5 | $0.00007 | $0.00045 |
Grade A, and why
godot-testing-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 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
Godot Testing Qa
Use these editor-integrated tools after opening the target Godot project. Paths must remain under res://.
Collision regression gate
Require a reasoned solid / trigger / query-only / none inventory,
actual body/shape and layer/mask readback, visual alignment, save/reopen,
off-script exploration, and pickup height/line-of-sight checks. A screenshot,
node count, successful tool call, or one prescribed route cannot pass this gate.
Report passed, failed, and not measured checks separately; distinguish native
physics queries or direct script calls from real-input and rendered playtests.
Load godot-physics (dcc-mcp-cli load-skill godot-physics --dcc-type godot)
and read its references/collision-intent.md before accepting the scene.
Use skill_refs__list with skill: godot-physics, then skill_refs__read
with that skill and the returned path. The reference belongs to that skill;
do not resolve it relative to this skill or assume sibling filesystem access.
If it is unavailable, report the missing guidance and leave collision acceptance
unverified rather than silently skipping the gate.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +17 lines · +13 tokens per session 1cfd267b10a3
- 1mo ago First seen · 21 lines · 55 tokens per session scan A a1cbbe45a33f
godot-testing-qa is a skill published in the GitHub repository dcc-mcp/dcc-mcp-godot (3 stars, last pushed 2d ago), licensed MIT. It adds 68 tokens to every session and 453 once invoked, about $0.0003 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-08-31.
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.
unreal-playtest-agent
Domain skill - run screenshot-light PIE playtest episodes with structured entity observations, bounded semantic actions, transition polling, and in-memory traces for QA and external policy or RL runners.
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.
hearth-playtest
Let the engine hunt bugs for you — bot playtesting via hearth sweep. Seeded bot policies (mash/idle/wander/seek) play a scene headlessly across many seeds and report softlocks, crashes, stuck states, and unmet objectives as a compact evidence report; objectives double as executable acceptance criteria; a failing seed…
procgen-design
Design procedural content systems with seeds, constraints, and validation gates so generated output stays fun and shippable.