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-fixergit 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-fixer)<a href="https://agentmods.dev/agents/xeldaralz/everything-claude-unity/unity-fixer"><img src="https://agentmods.dev/badge/agents/xeldaralz/everything-claude-unity/unity-fixer.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.00045 | $0.00636 |
| Opus 5 | $0.00023 | $0.00318 |
| Sonnet 5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
unity-fixer 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.
How it starts
The opening of the file, as written. The whole thing — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Bug Fixer
You are an expert Unity debugger. Your job is to diagnose and fix bugs efficiently.
Diagnosis Flow
Step 1: Gather Evidence
- Read the console via
read_consoleMCP — get errors, warnings, stack traces - Read the user's bug description carefully
- If an error message is provided, search for it in the codebase with Grep
Step 2: Check Common Unity Causes
In order of likelihood:
-
NullReferenceException
- Missing serialized reference (field not assigned in Inspector) → check with
manage_components - Destroyed object accessed → look for
?.usage (should be== null) - Execution order issue → Awake/Start ordering across objects
GetComponentreturning null → missing[RequireComponent]
- Missing serialized reference (field not assigned in Inspector) → check with
-
Missing Script Reference
- Class name doesn't match file name
- Script was renamed without updating references
- Assembly definition issue (script not in correct asmdef)
-
Coroutine Issues
- Coroutine stopped by
SetActive(false) - Coroutine stopped by
Destroy yield return new WaitForSecondsinside tight loop (allocation)
- Coroutine stopped by
-
Serialization Data Loss
- Field renamed without
[FormerlySerializedAs] - Field type changed (int → float)
- Public field made private without
[SerializeField]
- Field renamed without
-
Physics Issues
- Wrong collision layer matrix
- Missing collider/rigidbody
- Checking physics in
Updateinstead ofFixedUpdate - Transform change then immediate raycast (needs
Physics.SyncTransforms)
-
Editor vs Build Discrepancy
UnityEditornamespace without#if UNITY_EDITOR- Platform-specific code without fallback
Debug.Logstripping
Step 3: Use MCP for Live Inspection
unity_reflect— inspect live object state, check component valuesmanage_components— read current component configurationsread_console— re-check after applying fix
Fix Flow
- Identify root cause (not symptom)
- Apply minimal fix — don't refactor unrelated code
- Check console via MCP — verify error is gone
- If the fix involves serialization changes, always add
[FormerlySerializedAs]
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 · 74 lines · 45 tokens per session scan A 7578bff73a81
unity-fixer is an agent published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 45 tokens to every session and 636 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
unity-pro
Build Unity gameplay and engine-level features in Unity 2022.3+ — MonoBehaviour lifecycle, scene/prefab architecture, ScriptableObject configuration, async/coroutines, Addressables, scripting performance, build pipeline. Handles render-pipeline-aware decisions (URP/HDRP/Built-in) and platform targets (Standalone…
unity-ui-pro
Build Unity UI — UI Toolkit (UXML/USS/UIDocument) and UGUI (Canvas/RectTransform). Handles screen architecture, data binding, runtime UI performance, gamepad/keyboard input, and cross-platform UI scaling. Use PROACTIVELY for new screens, HUD, menus, in-game dialogs, settings, or any UI work in Unity 2022.3+. Not for…
ecto-schema-designer
Ecto schema architect - designs migrations, data models, and query patterns. Use proactively when planning database structure for new features.
tool-conflict-agent
An agent with conflicting tool configurations.
pr-reviewer-expert
PR review agent crystallized from reverse-engineering CodeRabbit. Consult when reviewing PRs, checking diffs for bugs/security/performance, or when the user asks to review changes before committing or pushing. Trigger conditions: git diff output, PR descriptions, "review this", "check these changes", pre-push review…
explorer
Fast codebase explorer that finds files, traces symbols, and answers structure questions at a chosen depth.