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-extract-author/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-extract-author)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-extract-author"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-extract-author/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-extract-author"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-extract-author.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.00174 | $0.03759 |
| Opus 5 | $0.00087 | $0.01879 |
| Sonnet 5 | $0.00035 | $0.00752 |
| Haiku 4.5 | $0.00017 | $0.00376 |
Grade A, and why
yume-extract-author 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 11d 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 — 374 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-extract-author
You are the stage-5 author for Yume's text-to-world pipeline.
You read a SEMANTIC MAP + CLASS CATALOG (and optionally a HEIGHTMAP),
then you write a custom Python script that extracts entity
positions / biome masks / rotations from the semantic map and emits
the final extracted.json that drives the rest of the pipeline.
⚠ CURRENT PIPELINE (2026-05-27). The per-scene-LLM-script flow below is the ORIGINAL extraction approach. It has been largely SUPERSEDED by a deterministic strategy-library path:
tools/visual_layout/compose_world.pyreadsdata/lib/extraction_strategies.json(per-class strategy: extraction method, rotation rule, fit-to-mask, variant buckets, kit mesh, albedo override) and dispatches vialib_extract_dispatch.dispatch_extraction— no per-scene script needed. compose_world writes the MAP layer (entity defs + placements + biome ground + water + roads); a separatecompose_shell.pyadds the presentation layer (camera/player/input/ lighting/.tscn) so a map generator never decides how you view or control the world. Buildings render as kit-of-parts composite meshes (floor-tiered houses, townhall/bridge/wall kits) — seeyume-asset-designer§ Strategy C2. New classes = new JSON entries inextraction_strategies.json(no code). Backups NEVER go in the engine-globbedentities/dir — use<game>/_snapshots/(see.claude/rules/data-demo.md). This skill remains the reference for the LLM-as-parser fallback when a scene's extraction needs custom routing the strategy library can't express.
When to invoke
- After stage 2 (catalog) and stage 3 (semantic map) and stage 4 (heightmap) have all produced their artifacts
- Before stage 6 (asset prompts) or stage 7 (engine wiring)
When NOT to invoke
- For HUD / screen extraction — those use compose_hud / compose_screen
- For raw photoreal-to-flat conversion — that's the SAME stage 5 pipeline but the prompt+harness is what processes it; this skill writes the script, not the prompt
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.
- 11d ago First seen · 374 lines · 0 tokens per session scan A b5a9f122d8ad
yume-extract-author is a skill published in the GitHub repository kamwoh/yume (21 stars, last pushed 2mo ago), licensed MIT. It adds 174 tokens to every session and 3,759 once invoked, about $0.0009 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".