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.
git 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-plan)<a href="https://agentmods.dev/commands/idocohen560/claude-unity-game-studio/uw-cmd-plan"><img src="https://agentmods.dev/badge/commands/idocohen560/claude-unity-game-studio/uw-cmd-plan.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.00430 |
| Opus 5 | $0.00000 | $0.00215 |
| Sonnet 5 | $0.00000 | $0.00086 |
| Haiku 4.5 | $0.00000 | $0.00043 |
Grade A, and why
uw-cmd-plan 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 4d 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-plan — 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-plan — Planning Workflow
Break a feature or sprint into actionable tasks with clear acceptance criteria.
Steps
1. Define the Feature
Ask the user:
- What feature or sprint goal are we planning?
- Which GDD scenario(s) does this map to?
- Are there dependencies on existing systems?
2. Architecture Check
Read docs/TDD.md to understand:
- Which assemblies are involved
- Data flow between systems
- Any API constraints
3. Task Breakdown
Create a numbered task list with:
- Task name (action-oriented: "Implement X", "Create Y")
- Estimated complexity (S/M/L)
- Dependencies (which tasks must complete first)
- Acceptance criteria (what "done" looks like)
- Skill (which skill handles this task)
4. Sprint Structure
## Sprint [N]: [Goal]
**Duration**: [X days/weeks]
| # | Task | Size | Depends On | Skill | Status |
|---|------|------|-----------|-------|--------|
| 1 | Create PlayerHealth SO | S | — | uw-scriptable-object-arch | pending |
| 2 | /uw-cmd-implement-feature: damage system (incl. game feel) | M | 1 | uw-game-feel-integrator | pending |
| 3 | /uw-cmd-implement-feature: health UI (incl. animations) | M | 1 | uw-ui-toolkit-binder | pending |
| 4 | Write health edge-case tests | S | 2 | uw-unity-test-runner | pending |
Game feel is embedded inside each
/uw-cmd-implement-featuretask — not a separate row. If deferred, mark withTODO(gamefeel).
5. Output
- Updated
docs/SprintPlan.md - If Linear MCP is connected, create tasks in Linear
- Task dependency graph (optional)
$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.
- 4d ago First seen · 48 lines · 0 tokens per session scan A 7a5d730a2851
uw-cmd-plan is a command published in the GitHub repository IdoCohen560/claude-unity-game-studio (18 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 430 tokens. A static security scan graded it A with 0 findings. It is 100% identical to uw-cmd-plan, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
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.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.