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-merchant-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-merchant-reviewer)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-merchant-reviewer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-merchant-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-merchant-reviewer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-merchant-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.00060 | $0.03844 |
| Opus 5.5 | $0.00024 | $0.01538 |
| Sonnet 5.5 | $0.00012 | $0.00769 |
| Haiku 4.5 | $0.00006 | $0.00384 |
Grade A, and why
yume-merchant-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 — 417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-merchant-reviewer
You are the merchant-reviewer for Yume — the genre-specific
reviewer for merchant / shopkeeping / item-shop GDDs. You run AFTER
the generic 15-axis yume-game-reviewer accepts; you apply the
8-axis merchant-strict review that catches concerns the generic
reviewer can't see.
Inputs and outputs
This skill runs as a forked skill (ADR 0082). It runs in its own subagent and does not see the chat history. The arguments and the files below carry all the input.
- Arguments. The game slug and the GDD path. Example:
demo_x docs/games/x/GDD.md. Read the GDD and any design files that it names. - Output. Append the merchant-genre section to
docs/games/<name>/review.md. Keep the generic findings. - 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.
Why this skill exists
A merchant game can pass all 13 generic axes (rich theme, clean mechanic table, decent scope, signature moments) and still SHIP SHALLOW because the generic reviewer can't catch:
- "3 customer archetypes" — but each wants the same 1 item type (no class-gear coverage matrix)
- "Daily cycle: morning + adventure + shop" — but no spec for durations, transitions, or distinct verbs (one-phase boredom)
- "Haggle is fun" — but no spec for the actual exchange shape
- "Debt drives tension" — but linear
gold/daycurve flattens the tension arc that makes an item-shop merchant game iconic - "Reputation matters" — but only affects price (no meta-progression)
- "Inventory: 20 slots" — but no UX plan for finding things
This skill is the strictest gate before content authoring begins. Catch these BEFORE rule sketches + JSON, where rework is 10x costlier.
Inputs
A GDD at docs/games/<name>/GDD.md (already accepted by generic
reviewer). Optionally: existing combining-design / economy-design /
story-design if Phase 1e ran.
Outputs
Append a "Merchant-genre review" section to the existing
docs/games/<name>/review.md. Don't replace the generic findings —
extend them.
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 Changed · +18 lines · -47 tokens per session 6b25ebdd8552
- 1mo ago First seen · 399 lines · 107 tokens per session scan A 60cc21e684e1
yume-merchant-reviewer is a skill published in the GitHub repository kamwoh/yume (25 stars, last pushed 10d ago), licensed MIT. It adds 60 tokens to every session and 3,844 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
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 4, 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.
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…
asset-audit
Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
hybrid-prototype
Fast-lane prototype skill for the hybrid workflow. Builds a playable prototype in 2-3 days with minimal process overhead. Designed for discovery phase.