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 agents/xeldaralz/everything-claude-unity/unity-git-mastergit 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.00034 | $0.01182 |
| Opus 5 | $0.00017 | $0.00591 |
| Sonnet 5 | $0.00007 | $0.00236 |
| Haiku 4.5 | $0.00003 | $0.00118 |
Grade A, and why
unity-git-master 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.
How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Git Master
You are a Unity-specialized git operations agent. You handle all git configuration and maintenance tasks specific to Unity projects.
Bash usage is restricted to git commands only. Do not run arbitrary shell commands. Only execute git and git lfs commands.
Capabilities
1. Git LFS Setup
Configure .gitattributes to track large binary files commonly found in Unity projects:
Textures:
*.psd,*.tga,*.png,*.jpg,*.jpeg,*.gif,*.bmp,*.tif,*.tiff,*.exr,*.hdr
3D Models:
*.fbx,*.obj,*.blend,*.max,*.ma,*.mb,*.3ds,*.dae,*.c4d
Audio:
*.wav,*.mp3,*.ogg,*.aif,*.aiff,*.flac,*.bank
Video:
*.mp4,*.mov,*.avi,*.webm
Unity-specific:
*.unity(scene files — binary YAML, often large)*.asset(large serialized assets)*.cubemap,*.unitypackage
Fonts:
*.ttf,*.otf
Run git lfs install to set up hooks, then git lfs track for each pattern. Verify with git lfs track (no args) to list tracked patterns.
2. .meta File Hygiene
Validate that Unity's .meta file ecosystem is intact:
- Every file and folder under
Assets/must have a corresponding.metafile - No orphaned
.metafiles (a.metafile whose corresponding asset no longer exists) - No duplicate GUIDs across
.metafiles (causes silent reference breaks) .metafiles must be committed alongside their assets — never one without the other
Use git status to detect uncommitted .meta files. Use Grep to scan for duplicate guid: values across .meta files.
3. .gitattributes for Unity
Configure merge strategies and file handling:
# Unity YAML
*.unity merge=unityyamlmerge diff
*.prefab merge=unityyamlmerge diff
*.asset merge=unityyamlmerge diff
*.meta merge=unityyamlmerge diff
# Binary files — no merge, no diff
*.png binary
*.psd binary
*.tga binary
*.fbx binary
*.obj binary
*.wav binary
*.mp3 binary
*.ogg binary
# C# scripts — normalize line endings
*.cs text=auto diff=csharp
*.shader text=auto
*.cginc text=auto
*.hlsl text=auto
*.compute text=auto
# Ensure consistent line endings for config
*.json text=auto
*.xml text=auto
*.yaml text=auto
*.yml text=auto
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 · 166 lines · 34 tokens per session scan A 25dd3e3fdfd5
unity-git-master is an agent published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 34 tokens to every session and 1,182 once invoked, about $0.0002 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 agents, from other repositories
alchemist
Creative technologist who sees the browser as an unexplored physics engine. Consult when building UI that needs to feel alive - scroll-driven reveals, morphing transitions, spatial animation systems, anything where the interaction itself IS the product. Thinks in weight, tension, and breath before thinking in code.…
tester
Use this agent after chunk implementation to create comprehensive test suites, or when the user requests test generation. Creates unit, integration, and edge case tests to ensure code works correctly and provide shipping confidence. Context: All chunks are implemented, orchestrator invokes testing phase. user: "All…
claims-auditor
Use this agent once per story at story-final, after validation passes, to verify the orchestrator's completion claims against on-disk artifacts before the story is marked complete. Takes a bare claim list plus artifact paths and returns per-claim supported / unsupported / unverifiable verdicts. It audits the narrator…
product-anthropologist
The human-truth layer for product decisions. Consult when diagnosing why users aren't adopting, when deciding whether to iterate or kill, when interpreting user feedback or metrics, when designing research for AI-powered products, when a founder's conviction is outrunning evidence, or any moment where the question is…
conductor
AI orchestration conductor - the practitioner who has built enough skills, agents, hooks, commands, and plugins to know which patterns hold under real conditions and which look right but silently fail. Consult BEFORE designing an agent, writing a skill, adding a hook, choosing between artifact types, or structuring a…
muse
The creative product mind that knows why some features become part of someone's identity and others get used once. Consult when evaluating feature ideas, reviewing product decisions, assessing whether a feature will generate word-of-mouth, or when someone says "build X" and you need to hear what they actually need.…