Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add commands/idocohen560/claude-unity-game-studio/uw-cmd-creategit clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studioWrote 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/commands/idocohen560/claude-unity-game-studio/uw-cmd-create)<a href="https://agentmods.dev/commands/idocohen560/claude-unity-game-studio/uw-cmd-create"><img src="https://agentmods.dev/badge/commands/idocohen560/claude-unity-game-studio/uw-cmd-create.svg" alt="Measured on agentmods" 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.00471 |
| Opus 5 | $0.00000 | $0.00235 |
| Sonnet 5 | $0.00000 | $0.00094 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
uw-cmd-create 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 2d 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.
This is a copy
100% identical to uw-cmd-create — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
/uw-cmd-create — Code Creation Workflow
Generate isolated code following a test-driven development approach.
Scope: Utilities, helpers, data classes, editor tools, and backend systems with no direct game feel. For gameplay features: use
/uw-cmd-implement-featureinstead.
Skills
Load uw-unity-feature-scaffold from .claude/skills/uw-unity-feature-scaffold/SKILL.md.
Load uw-unity-test-runner from .claude/skills/uw-unity-test-runner/SKILL.md.
Steps
1. Understand the Requirement
- Which GDD scenario does this implement?
- Read the relevant TDD section for architecture constraints.
- Check
docs/ProjectConfig.yamlfor package versions and technology choices.
2. Scaffold the Feature
Use uw-unity-feature-scaffold skill:
- Feature folder structure
- Assembly Definition (
.asmdef) - Test Assembly Definition
3. Write Tests First
Use uw-unity-test-runner skill:
- Convert the Gherkin scenario to NUnit test(s).
- Write the test — it should fail because the implementation doesn't exist yet.
4. Implement
Write the minimal code to make tests pass:
- Follow
CLAUDE.mdrules (serialization, caching, thread safety) - Follow
docs/CODING_STANDARDS.mdformatting - Follow
docs/NAMING_CONVENTIONS.mdfor identifiers - Use
GameDebugfor debug logging - If creating SO data/events, follow
uw-scriptable-object-archpatterns - If creating DI services, follow
uw-dependency-injectionpatterns (whenarchitecture_pattern: "di-first")
5. Run Tests
- Via Unity MCP
run_testsif available. - Otherwise, instruct user to run in Test Runner.
- All tests must pass before proceeding.
6. Commit
- Feature branch:
feature/{feature-name} - Commit message:
feat({feature}): {description} - Follow
docs/GIT_CONVENTIONS.md
7. Output
- Working feature with passing tests
- Feature committed to a branch
$ARGUMENTS
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.
- 2d ago First seen · 54 lines · 0 tokens per session scan A aaa3af67db88
uw-cmd-create is a command published in the GitHub repository IdoCohen560/claude-unity-game-studio (17 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 471 tokens. A static security scan graded it A with 0 findings. It is 100% identical to uw-cmd-create, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
prompt-evolve
Closed prompt-evolution loop: turn a lesson into a candidate agent prompt, gate it on held-out evals, promote only if it beats the baseline. SIA Meta→Target→Feedback ported to greatcto.
bug
Reproduce then TDD-fix a ready-for-agent bug ticket in this checkout. Web bugs get a browser repro first.
coder
Autonomous code generation with batch file operations.
qec-sinter
Generate Sinter task templates and configure community benchmark harnesses for QECTOR decoders.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.