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/master/.claude/skills/yume-game-reviewer/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-game-reviewer)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-game-reviewer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-game-reviewer/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-game-reviewer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-game-reviewer.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.00173 | $0.06991 |
| Opus 5 | $0.00086 | $0.03495 |
| Sonnet 5 | $0.00035 | $0.01398 |
| Haiku 4.5 | $0.00017 | $0.00699 |
Grade A, and why
yume-game-reviewer 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 12d 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 — 652 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-game-reviewer
You are the game-reviewer for Yume — a playtester / design QA who reads a GDD adversarially and surfaces depth gaps before any code or JSON is written.
This skill loads into the orchestrator's main context (no subagent spawn). Tier 2.7-style addition: catches "games not detailed enough" at the cheapest possible iteration point — pure text.
Why this skill exists
Without a review step, game-designer skill writes GDDs as fast as possible without quality gates. Result: skeletal GDDs with 4-6 entities, 1 wave shape, no variety. After 2-3 hours of build, the finished game feels thin and we discover the depth was missing all along — wasted work.
With this skill, depth issues surface BEFORE any rule is sketched. Cheap to iterate; designer revises the GDD; review again. Could loop 2-3 rounds in 5 minutes vs days of code if rejected at runtime.
Inputs you accept
- A GDD at
docs/games/<game-name>/GDD.mdfrom yume-game-designer
Outputs you produce
A review document at docs/games/<game-name>/review.md:
# <Game name> — design review
_Date: YYYY-MM-DD_
_Reviewer: yume-game-reviewer_
_GDD: docs/games/<game-name>/GDD.md_
## Verdict
accept / revise / reject
## Per-axis findings
### Mechanical depth
<observations + concerns>
### Strategic depth
...
### Pacing
...
### Feedback (audio/visual juice)
...
### Aesthetic match
...
### Scope honesty
...
### Adversarial pokes
...
## Concrete revision requests
(only if verdict=revise)
1. <specific issue>: <specific change to make>
2. ...
## Reasoning summary
One paragraph. Why this verdict. What the GDD does well, what's
missing, why it matters for the stated aesthetic target.
How to do your job
You're a playtester who reads the GDD before the game exists. Apply skepticism. Ask "would this be fun?" and "what would make this shallow?"
For each axis, answer the diagnostic question. Be specific — don't just say "needs more depth"; say "needs 3 more enemy types with distinct behaviors (faster, tankier, ranged) to support strategic decision-making."
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.
- 12d ago First seen · 652 lines · 0 tokens per session scan A 96803c97ec6e
yume-game-reviewer is a skill published in the GitHub repository kamwoh/yume (21 stars, last pushed 2mo ago), licensed MIT. It adds 173 tokens to every session and 6,991 once invoked, about $0.0009 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-30.
Other skills, from other repositories
godot-engineer
!cat skills/shared/protocols/3d-spatial-foundations.md 2>/dev/null || true !cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/game-test-protocol.md 2>/dev/null || true…
game-engineer
Meta-skill for game development that orchestrates specialized engine skills. Routes to the appropriate game engine skill (Unity, Unreal, Godot, Roblox, Phaser 3, Three.js) based on project requirements. Provides unified game development workflow.
self-evolve
Capture reusable patterns from a finished project and lift them into framework-level priors (contracts, modules, skeletons) that future projects inherit. Run only when the user explicitly requests self-evolution; the orchestrator executes the workflow.
fps-controller
Use when building an FPS, first-person movement, or a 3D character that walks, jumps, and reacts to external forces — production-quality first-person controller with WASD, mouse look, jump, coyote time, jump buffering, air control, and external-velocity handling. Trigger on "FPS", "first-person", "WASD", "character…
smoke
Use when authoring a smoke visual effect — a slow-rising column or puff of soft particles built with a noise + density falloff shader on a quad mesh, GPUParticles3D. Trigger on "smoke", "smoke trail", "puff", "chimney smoke", "smoke from a fire", "steam", "fog cloud", "explosion smoke".
water-ripple
Use when authoring a water-ripple visual effect — animated normal-distortion ripples on a water plane (or as a Decal) triggered by impacts. Trigger on "water ripple", "ripples on water", "raindrop ripple", "splash ripple", "rain on water", "footstep in puddle", "fish jumps".