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-save-policy-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-save-policy-designer)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-save-policy-designer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-save-policy-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-save-policy-designer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-save-policy-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.00044 | $0.01913 |
| Opus 5.5 | $0.00018 | $0.00765 |
| Sonnet 5.5 | $0.00009 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00191 |
Grade A, and why
yume-save-policy-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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-save-policy-designer
You are the save policy designer for Yume. Your job: decide what persists across sessions for each game.
This skill loads into the orchestrator's main context (Tier 2.6 — no subagent spawn).
Why this skill exists
Save/load is universal in shipping games but underspecified per-game. Without a policy specialist, common failure modes:
- Saves miss critical state (player progress restarts after reload)
- Saves include too much (every projectile, every tile — saves balloon)
- No autosave triggers (player rage-quits after losing 30 minutes)
- Save schema changes silently break old saves
- Persistent entities don't actually persist across chunks (per ADR 0014)
This skill produces save_policy.json per ADR 0010's schema.
Inputs
- A GDD at
docs/games/<game>/GDD.md(mentions save / progress / achievements / persistence) - Optional: world-plan (named NPCs that should persist), level-design (level-transition triggers), economy-design (currencies that should persist)
Outputs
A save policy at data/<game>/save_policy.json (per ADR 0010 schema).
Core questions to answer
1. What world_state keys persist?
Walk through the game's world_state usage. For each key, decide: persist vs reset on new game vs purely runtime.
Examples:
current_level— persist (player resumes at correct level)score— persist (long-term progress)tutorial_step— persist (don't re-do tutorial after reload)achievements_unlocked— persist (cross-save persistence)tick— runtime only (reset; engine recomputes)_pending_level_transition— runtime only (engine internal)last_input_action— runtime only
Rule of thumb: persist if the player would feel cheated by losing it.
2. Which entity tags survive?
Per ADR 0014, persistent-tagged entities survive chunk eviction. The save policy further filters which TAGS the engine SERIALIZES.
Typical patterns:
named_npc— persist (each NPC has identity + state)shop/landmark/chest— persist (positional + state)pickup/monster/projectile— DON'T persist (transient)terrain/wall— DON'T persist (reload from chunk JSON)
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 · +3 lines · +44 tokens per session 815aecce0dd1
- 1mo ago First seen · 249 lines · 0 tokens per session scan A 32b7b5474122
yume-save-policy-designer is a skill published in the GitHub repository kamwoh/yume (25 stars, last pushed 10d ago), licensed MIT. It adds 44 tokens to every session and 1,913 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.