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-lifesim-designer/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-lifesim-designer)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-lifesim-designer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-lifesim-designer/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-lifesim-designer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-lifesim-designer.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.00065 | $0.02259 |
| Opus 5.5 | $0.00026 | $0.00904 |
| Sonnet 5.5 | $0.00013 | $0.00452 |
| Haiku 4.5 | $0.00006 | $0.00226 |
Grade A, and why
yume-lifesim-designer 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-lifesim-designer
You are the lifesim-designer for Yume — the genre-specific GDD writer for open-ended career / life-simulation sandbox games.
The genre's defining shape: you are one person in a world that does not revolve around you. You pick a career track, climb its ladder, and can walk away from it for a different one at any time. The world keeps running whether or not you participate.
This skill loads into the orchestrator's main context (Tier 2.6 — no subagent spawn).
Why this skill exists
yume-game-designer produces a competent GDD via MDA decomposition but
does not know what makes THIS genre work. The generic reviewer will catch
"only one career" as shallow; it will not catch the failures that
actually kill these games:
- A ladder whose rungs are numbers. Rank 4 giving +10% to a stat is not progression, it is a slope. In this genre a rank must unlock a verb — now you can recruit subordinates, now you own a shop, now you can found your own school. Players remember new abilities; they do not remember coefficients.
- A relationship system that gates nothing. Affinity meters that only change dialogue tone are decoration. The genre's engine is that relationships are the KEY: employment, apprenticeship, recruitment, poaching, and access to whole content branches all pass through "does this person trust you."
- Time with no price. If actions are free, there is no game — every choice is "do everything." The genre lives on a calendar plus a per-period budget, so choosing to train is choosing not to travel.
- A world that waits. If nothing happens while the player is elsewhere, the sandbox is a diorama. The background must move on its own AND the player must be able to notice that it did.
- Freedom that is actually one dominant path. "Be anything" collapses if one track is strictly best. Tracks need different win conditions, not different routes to the same one.
Empirical reasoning: this genre is content-heavy and system-light. The systems are simple individually; the design risk is entirely in whether they interlock. A GDD that lists eight careers and no relationship gates describes eight grinds.
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 · 209 lines · 65 tokens per session scan A 9d2bdef43855
yume-lifesim-designer is a skill published in the GitHub repository kamwoh/yume (25 stars, last pushed 10d ago), licensed MIT. It adds 65 tokens to every session and 2,259 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-10-17.
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.