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/xeldaralz/everything-claude-unity/unity-workflowgit clone --depth 1 https://github.com/XeldarAlz/everything-claude-unityWrote 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/xeldaralz/everything-claude-unity/unity-workflow)<a href="https://agentmods.dev/commands/xeldaralz/everything-claude-unity/unity-workflow"><img src="https://agentmods.dev/badge/commands/xeldaralz/everything-claude-unity/unity-workflow.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 | $0.00024 | $0.01328 |
| Opus 5 | $0.00012 | $0.00664 |
| Sonnet 5 | $0.00005 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
unity-workflow 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 3d 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/unity-workflow — Full Development Pipeline
Orchestrate a complete development workflow for: $ARGUMENTS
This command runs a 4-phase pipeline: Clarify → Plan → Execute → Verify. Each phase requires explicit user confirmation before proceeding to the next.
Phase 1: Clarify
Interview the user to build a complete requirements picture. Ask about:
- Core mechanic / feature purpose — what does it do? What problem does it solve?
- Target platform — mobile (iOS/Android), desktop, WebGL, VR?
- Performance constraints — target FPS? Memory budget? Draw call limit?
- Unity subsystems involved — physics? UI? animation? audio? networking?
- Integration points — what existing systems does this touch?
- Acceptance criteria — how do we know it's done? What should we test?
Produce a Requirements Summary with all answers consolidated. Ask the user to confirm before proceeding.
If the user provided a detailed description in $ARGUMENTS and the requirements are clear, you may present the summary directly for confirmation rather than asking each question individually.
Phase 2: Plan
Based on confirmed requirements:
- Scan the project — use
unity-scout(haiku) for fast codebase exploration: read CLAUDE.md, find relevant existing scripts, map assembly structure - Identify subsystems — which Unity packages and skills are involved?
- Assess complexity using the model-routing skill heuristics:
- Count estimated files to create/modify
- Check for complexity keywords in the task description
- Identify risk factors (serialization changes, networking, platform-specific, threading)
- Rate as simple (1-2 files, no risk) / moderate (3-8 files, some risk) / complex (9+ files, high risk)
- Choose execution strategy based on complexity:
- Simple →
unity-coder-lite(sonnet) — faster, cheaper - Moderate →
unity-coder(opus) — deeper reasoning - Complex → multiple agents via
/unity-team - Specialized → route to domain agent:
unity-prototyper,unity-ui-builder,unity-network-dev,unity-shader-dev
- Simple →
- Generate implementation plan:
- Scripts to create/modify (with file paths and assembly placement)
- Scene changes needed (GameObjects, components, physics layers)
- Dependencies on existing systems
- Risk areas (serialization, platform-specific, performance)
- Estimated complexity and chosen agent tier with rationale
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.
- 3d ago First seen · 135 lines · 24 tokens per session scan A 3fe77f54481d
unity-workflow is a command published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 24 tokens to every session and 1,328 once invoked, about $0.0001 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 commands, from other repositories
become
Agent crystallization command. Studies a tool, role, or person and produces a portable 9-section agent that inhabits the domain - with beliefs, scar tissue, and instincts.
notebook
Low-ceremony capture for ideas (half-formed, want to mature into stories), todos (concrete actions), and notes (durable project/team facts for future recall). One-line capture, conditional elaboration AUQ. Use BEFORE thoughts get forced into stories.
stats
Show token-saver compression statistics and savings.
cycle-start
Activate a cycle and start implementing its stories.
story-continue
Resume an interrupted story from where you left off.
story-archive
Move a story from a cycle back to the backlog.