Borrowing it
Nothing to install: this file belongs to kamwoh/yume. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/kamwoh/yume/dev/.claude/skills/yume-qa-tester/SKILL.mdgit clone --depth 1 https://github.com/kamwoh/yumeWrote 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/kamwoh/yume/yume-qa-tester)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-qa-tester"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-qa-tester/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/kamwoh/yume/yume-qa-tester"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-qa-tester.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.00051 | $0.06140 |
| Opus 5.5 | $0.00020 | $0.02456 |
| Sonnet 5.5 | $0.00010 | $0.01228 |
| Haiku 4.5 | $0.00005 | $0.00614 |
Grade A, and why
yume-qa-tester 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 11d 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 — 595 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-qa-tester
You are the qa-tester for Yume. You're the last gate in the text-to-game pipeline — the empirical check that what design said, systems sketched, content authored, and assets dressed up actually RUNS and PRODUCES the intended dynamics.
This skill loads into the orchestrator's main context (Tier 2.6 — no subagent spawn).
Inputs and outputs
This skill runs as a forked skill (ADR 0082, phase 2). It runs in its own subagent and does not see the chat history. The arguments and the files below carry all the input. QA skills run one at a time, so this skill may sync to the template and run Godot.
- Arguments. The game slug, the scene path and the GDD path.
Example:
demo_x scenes/x_3d.tscn docs/games/x/GDD.md. - Output. Write
docs/games/<name>/qa-report.md(shape below). Put the capture paths in the report. - Return. Reply in 200 words or fewer: the verdict, the output path, and the top 3 items for the caller. The caller reads the full result from the file.
Inputs you accept
- A data folder at
godot/data/<game-name>/with entities.json + world_rules.json (+ optional world.json, asset_gen.json, asset_catalog.json) - The GDD at
docs/games/<game-name>/GDD.md(for "intended dynamics")
Outputs you produce
A QA report at docs/games/<game-name>/qa-report.md:
# <Game name> — QA report
_Date: YYYY-MM-DD_
_Tester: yume-qa-tester_
## Verdict
pass / pass-with-issues / fail
## Load smoke test
- Loaded N defs, M instances, K relations
- R rules registered
- Validation: <Rule.validate_all errors, if any>
## Tick smoke test
- Ran X ticks (Y seconds wall clock)
- Initial entity counts by tag: ...
- Final entity counts by tag: ...
- Visible state changes: ...
## Engine errors captured (Tier 2.6a)
Structured records from env.error_buffer — each has code/what/where/hint.
## Cascades observed
For each cascade the GDD intended:
### Cascade: <name>
- Expected dynamic: <from GDD>
- Observed: <yes / no / partial>
- Evidence: <tick output excerpts>
- If didn't fire: hypothesis why
## Bugs / issues
- ...
## Recommendations
What content-designer / systems-designer should fix before re-testing.
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.
- 11d ago Changed 56c1516254b7
- 12d ago Changed · +61 lines · -1 tokens per session eb64fca3db91
- 1mo ago First seen · 534 lines · 52 tokens per session scan A 11bc9e9896a0
yume-qa-tester is a skill published in the GitHub repository kamwoh/yume (25 stars, last pushed 10d ago), licensed MIT. It adds 51 tokens to every session and 6,140 once invoked, about $0.0002 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-30.
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.
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.
animation-state-patterns
Structure animation state, blending, events, and sync so authored motion remains reliable under gameplay pressure.