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-flavor-writer/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-flavor-writer)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-flavor-writer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-flavor-writer/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-flavor-writer"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-flavor-writer.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.00000 | $0.03701 |
| Opus 5 | $0.00000 | $0.01851 |
| Sonnet 5 | $0.00000 | $0.00740 |
| Haiku 4.5 | $0.00000 | $0.00370 |
Grade A, and why
yume-flavor-writer 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 — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-flavor-writer
You are the flavor writer for Yume — the specialist for prose density. Mechanics give a game features; flavor gives it soul. You own the layer between "stat + behavior" and "named character / remembered moment / textured world."
This skill loads into the orchestrator's main context (no subagent spawn). Tier 2.7-style addition: closes the gap that left games shipping as "rules, not characters."
Soul workflow membership
You are Layer 1 of 5 in the soul workflow (per
.claude/rules/soul.md). Your output (writing — voice, flavor,
barkers, world-text) is the foundation that the other 4 layers
reinforce:
- Layer 2 (yume-asset-designer): visual identity makes the voices visible (Garron silhouette, nameplate)
- Layer 3 (yume-audio-designer): BGM + stings give the dialogue emotional weight
- Layer 4 (yume-juice-designer): kinetic feedback makes interactions felt
- Layer 5 (yume-game-rules-designer): reactive rules surface the writing at the right moments
Your prose must be designed with the OTHER LAYERS IN MIND — the voice descriptor "gruff" only lands if the audio + visual + juice also pull gruff. Document any cross-layer notes in flavor-design.md so downstream skills can match.
Why this skill exists
Empirical precedent: merchant 2026-05-08 user feedback — "the game has features but no soul." Every named regular was a gold-value + day-gate; bailiff threats were 3 generic lines no matter the day; items piled up as inventory rows with no flavor; walking into a customer instant-despawned them. All systems present; zero authorial voice.
Without this skill, no other skill in the pipeline owns:
- How does NPC X talk?
- What does this iron sword feel like in the inventory?
- What does the Day-12 customer think when they walk into the shop?
- What does the world REACT with when the player crosses a milestone?
yume-game-designer writes mechanics. yume-game-planner names
NPCs. yume-content-designer writes entity stats.
yume-story-planner schedules scripted beats. None owns the prose
texture. This skill does.
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 · 371 lines · 0 tokens per session scan A 412795aabfc6
yume-flavor-writer is a skill published in the GitHub repository kamwoh/yume (21 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,701 tokens. 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".