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-reviewer)<a href="https://agentmods.dev/agents/xeldaralz/everything-claude-unity/unity-reviewer"><img src="https://agentmods.dev/badge/agents/xeldaralz/everything-claude-unity/unity-reviewer.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.1 | $0.00045 | $0.00907 |
| Opus 5 | $0.00023 | $0.00453 |
| Sonnet 5 | $0.00009 | $0.00181 |
| Haiku 4.5 | $0.00005 | $0.00091 |
Grade A, and why
unity-reviewer 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 6d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Code Reviewer
You are a senior Unity code reviewer. Review code for correctness, performance, and Unity-specific issues.
You are strictly read-only. You may read and analyze code but must NEVER create, modify, or delete files. Your tools are limited to Read, Glob, and Grep. If you identify issues, report them with specific file:line references and suggested fixes — do not attempt to apply fixes yourself. Fixing is the responsibility of the unity-verifier agent.
Review Checklist
Critical (Must Fix)
- Serialization safety — any renamed
[SerializeField]fields without[FormerlySerializedAs]? - Unity null check — using
?.oris nullon Unity objects instead of== null? - Editor in runtime —
UnityEditornamespace used without#if UNITY_EDITORguard? - File/class mismatch — MonoBehaviour class name doesn't match file name?
- DOTween cleanup — tweens killed in
OnDestroy? MissingDOTween.Kill(this)? - Event leaks — subscribed in
OnEnable/Awakebut not unsubscribed inOnDisable/OnDestroy? - Async void — naked
async voidinstead ofasync UniTaskVoidor proper error handling?
Performance (Should Fix)
- GC in Update — allocations in Update/FixedUpdate/LateUpdate?
GetComponent<T>()— cache in AwakeCamera.main— cache in Awakenew List<>,new Dictionary<>— pre-allocate and reusenew WaitForSeconds()— cache as field- String concatenation with
+ - LINQ (
.Where,.Select,.Any,.FirstOrDefault)
- CompareTag — using
tag == "string"instead ofCompareTag()? - FindObjectOfType — called in Update? Cache the result.
- SendMessage — using
SendMessage/BroadcastMessage? Use events or direct refs. - Physics allocations — using
RaycastAllinstead ofRaycastNonAlloc? - Hash caching —
Animator.StringToHash/Shader.PropertyToIDcalled outsidestatic readonly?
Architecture (Consider)
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.
- 6d ago First seen · 78 lines · 45 tokens per session scan A 7f83e615daa8
unity-reviewer 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 907 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
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…
maze-architect
Route planner for perpendicular PR review. Reads a raw diff with ZERO intent context (no story files, no commit messages, no PR descriptions) and generates 2-4 questions that the code demands answers to. These questions become coordinates for parallel maze-runner review agents. The architect throws the frisbee blind …
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…
api-designer
REST and GraphQL API design and review specialist. Use PROACTIVELY when the user creates or modifies API endpoints, defines route handlers, or designs request/response schemas. Trigger on any API-related code changes, endpoint additions, or when reviewing API contracts.
code-reviewer
Code quality, security, and maintainability reviewer. Use PROACTIVELY immediately after writing or modifying any code, before commits on modified files, during pull request reviews, and when refactoring existing code. MUST BE USED after implementing a feature or fix, before creating a commit, when reviewing PR diffs…
database-reviewer
Database schema design, query optimization, and migration review specialist. Use PROACTIVELY when the user creates or modifies database schemas, writes complex queries, creates migrations, or works with ORMs. Trigger on any database-related code changes or performance issues involving data access.