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/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/agents/xeldaralz/everything-claude-unity/unity-git-master)<a href="https://agentmods.dev/agents/xeldaralz/everything-claude-unity/unity-git-master"><img src="https://agentmods.dev/badge/agents/xeldaralz/everything-claude-unity/unity-git-master/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/xeldaralz/everything-claude-unity/unity-git-master"><img src="https://agentmods.dev/badge/agents/xeldaralz/everything-claude-unity/unity-git-master.svg" alt="Reviewed on agentmods" width="80" 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.00034 | $0.01182 |
| Opus 5.5 | $0.00014 | $0.00473 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (25 stars, last pushed 6mo ago), licensed MIT. It adds 34 tokens to every session and 1,182 once invoked, about $0.0001 per session on Opus 5.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
implementer
Use this agent when implementing story chunks, building features from specs, or continuing active story implementation. Owns the implement → validate → refine loop for each chunk. Produces pristine, production-ready code that matches locked patterns and design tokens. Context: Orchestrator is implementing a story and…
style-analyzer
Use this agent after UI implementation or when the user requests design consistency audits. Ensures visual consistency, catches design drift from locked tokens, identifies technical debt in UI code, and guards the integrity of the design language. Context: Multiple UI components were built during the cycle. user…
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…
practitioner-reviewer
Practitioner review agent for /craft:research-verify. Reads verified claims and challenges them from practical experience - not sources. Catches claims that are "confirmed by docs but wrong in practice." Acts as the user's proxy when they can't review 44 claims manually. NOT a source-checker. Does not search the web.…
verifier
Verification agent for /craft:research-verify. Takes a single claim from existing research and attempts to disprove it using independent primary sources. Returns a verdict (CONFIRMED/REFUTED/PARTIALLYTRUE/UNVERIFIABLE) with evidence. NOT a researcher. Does not discover new topics or cast a wide net. Takes one claim…
vibe-environment-worker
Runs a vibe session's Vercel environment in the target repository for the vibe and handoff orchestrators. Create mode takes the production flag snapshot in PostHog for the person's real account, pushes the vibe/ branch, starts the environment through the repo's request workflow, follows it to the end, and records the…