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-initgit clone --depth 1 https://github.com/XeldarAlz/everything-claude-unityWhat 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.00029 | $0.00377 |
| Opus 5 | $0.00015 | $0.00188 |
| Sonnet 5 | $0.00006 | $0.00075 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
unity-init 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.
What it actually says
/unity-init — Project Setup
Scan this Unity project and generate a tailored CLAUDE.md configuration.
Steps
-
Read project info via MCP
project_inforesource to get Unity version, platform, and state. -
Scan Packages/manifest.json to detect installed packages:
- Render pipeline (URP, HDRP, or Built-in)
- Input System, Addressables, Cinemachine, Timeline, TextMeshPro
- Networking (Netcode, Mirror, Photon, Fish-Net)
- Third-party (DOTween, UniTask, VContainer, Zenject, Odin)
-
Scan for assembly definitions (
.asmdeffiles) — map the project's assembly structure. -
Scan for scenes — list all
.unityfiles inAssets/. -
Check existing CLAUDE.md — if one exists, preserve user customizations.
-
Generate CLAUDE.md with:
- Project overview (Unity version, render pipeline, detected packages)
- Assembly structure
- Scene list
- References to rules files (
.claude/rules/*.md) - Recommended skills based on detected packages
- MCP integration notes
- Key conventions summary
-
Report what was detected and configured. Suggest next steps:
- Review and customize the generated CLAUDE.md
- Install unity-mcp if not already present
- Try
/unity-auditfor a full project health check
Output
Present the results in a clear summary table showing what was detected and which skills are recommended.
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 · 44 lines · 29 tokens per session scan A f12a6810e7ca
unity-init is a command published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 29 tokens to every session and 377 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.
cycle-design
Design a cycle — create new cycles with planned stories, detail existing planning cycles, or quick-sketch a roadmap. Detects planning docs in .craft/planning/ and sources the cycle from them when relevant.
docs
Generate or update project documentation using the crystallized doc-writer agent. Two-pass: brief (analysis + plan) then generate (write docs). Detects first-run vs update automatically.
reflect
Apply captured learnings to improve the Craft harness and project patterns. Converts .learnings.yaml into permanent updates.
stats
Show token-saver compression statistics and savings.