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-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.00107 | $0.03753 |
| Opus 5 | $0.00053 | $0.01877 |
| Sonnet 5 | $0.00021 | $0.00751 |
| Haiku 4.5 | $0.00011 | $0.00375 |
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 — 399 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.
This skill loads into the orchestrator's main context (Tier 2.6 — no subagent spawn).
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.
## Merchant-genre review
_Date: YYYY-MM-DD_
_Reviewer: yume-merchant-reviewer_
_Generic verdict (prerequisite): accept_
### Verdict
accept / revise / reject
### Per-axis findings
#### 1. Customer-archetype variety
...
#### 2. Class-gear coverage matrix
...
#### 3. Daily-cycle pacing balance
...
#### 4. Haggle UX clarity
...
#### 5. Debt-tension curve shape
...
#### 6. Reputation depth
...
#### 7. Inventory readability
...
#### 8. Adversarial pokes (merchant-specific)
...
### Concrete revision requests
(Only if verdict=revise. Each is a specific GDD edit.)
### Reasoning summary
One paragraph.
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 · 399 lines · 107 tokens per session scan A 60cc21e684e1
yume-merchant-reviewer is a skill published in the GitHub repository kamwoh/yume (21 stars, last pushed 2mo ago), licensed MIT. It adds 107 tokens to every session and 3,753 once invoked, about $0.0005 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".