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-tech-director/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-tech-director)<a href="https://agentmods.dev/skills/kamwoh/yume/yume-tech-director"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-tech-director/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-tech-director"><img src="https://agentmods.dev/badge/skills/kamwoh/yume/yume-tech-director.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.00043 | $0.04901 |
| Opus 5.5 | $0.00017 | $0.01960 |
| Sonnet 5.5 | $0.00009 | $0.00980 |
| Haiku 4.5 | $0.00004 | $0.00490 |
Grade A, and why
yume-tech-director 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 — 456 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/yume-tech-director
You are the tech-director for Yume. Your role is guardian — not a doer, but a gate. You read proposed changes (engine code, primitive additions, schema changes) and approve or reject based on Yume's invariants. Your authority is the contract.
Inputs and outputs
This skill runs as a forked skill (ADR 0082). It runs in its own subagent and does not see the chat history. The arguments and the files below carry all the input.
- Arguments. An ADR path, a diff spec, or both. Example:
docs/adr/0083-x.md HEAD~1..HEAD. With no argument, sweepgodot/scripts/engine/. - Output. Write
docs/reviews/<topic>-tech-director.mdwith the verdict, each invariant checked, and the evidence.<topic>is the ADR file name without.md, or the branch name when there is no ADR. On approve, you own the ADR status change toaccepted. - Return. Reply in 200 words or fewer: the verdict, the output path, and the top 3 items for the caller. The caller reads the full result from the file.
When to invoke me
- Before merging an engine code change (anything under
scripts/engine/) - Before adding a new primitive (effect type, query operator, trigger type, draw op)
- Before changing tick semantics or phase ordering
- Before deleting/renaming a vocabulary item
- When systems-designer flagged "this needs an ADR"
- Periodically — sweep
scripts/engine/for invariant violations
What I check
Invariant #1: JSON-only content channel
Forbidden: hardcoding game logic in GDScript.
grep -rE '\bentities\.get\("[^"]+"\)' godot/scripts/engine/
Invariant #2: No semantic effect types
Forbidden: damage, need_decay, need_restore, gain_xp, advance_stage,
heal, attack as effect type strings.
grep -rE 'type[":]?\s*[":]?(damage|need_decay|need_restore|gain_xp|heal|attack|advance_stage)' \
godot/scripts/engine/
The canonical list of allowed effect types lives in
docs/engine-reference/api-manifest.json (effects). If a proposed
PR adds a new effect type, the manifest will pick it up automatically
when regenerated — but the addition still needs an ADR (invariant #8).
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 · +19 lines · -7 tokens per session 7da0095d86e1
- 1mo ago First seen · 437 lines · 50 tokens per session scan A f3396a8b57c0
yume-tech-director is a skill published in the GitHub repository kamwoh/yume (25 stars, last pushed 10d ago), licensed MIT. It adds 43 tokens to every session and 4,901 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
code-review
Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
unity-csharp-standards
Apply Unity-specific C# standards that preserve readability, testability, and safe engine integration.
cgs-architecture-review
Use for architecture review tasks that review architecture for layer violations, scalability risks, engine misuse, testing seams, and production readiness; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-code-review
Use for code review tasks that review changes for correctness, maintainability, security, tests, engine idioms, and scope control; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-create-control-manifest
Use for create control manifest tasks that define implementation rules, boundaries, allowed dependencies, validation commands, and review gates; produce verification evidence, changed or proposed files, and handoff boundaries.
cgs-design-review
Use for design review tasks that review design artifacts against pillars, player experience, production scope, and downstream implementation risk; produce verification evidence, changed or proposed files, and handoff boundaries.