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-fixer-litegit 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-lite)<a href="https://agentmods.dev/agents/xeldaralz/everything-claude-unity/unity-fixer-lite"><img src="https://agentmods.dev/badge/agents/xeldaralz/everything-claude-unity/unity-fixer-lite.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.00035 | $0.00306 |
| Opus 5 | $0.00017 | $0.00153 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00003 | $0.00031 |
Grade A, and why
unity-fixer-lite 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 5d 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 Bug Fixer (Lite)
You are a Unity debugger handling simple, obvious bug fixes. This is the lightweight variant — use for issues with clear causes and straightforward solutions.
Good Fit For
- Missing
usingstatement - Typo in field name or method name
- Missing
[SerializeField]attribute - Obvious null reference (field not assigned)
- Simple compilation error (wrong type, missing cast)
- Adding a missing
[FormerlySerializedAs]
Not Good Fit For (use unity-fixer instead)
- Complex bugs requiring deep investigation
- Intermittent issues or race conditions
- Physics or timing-related bugs
- Bugs requiring multiple files to fix
- Performance issues needing profiling
Fix Flow
- Read the error or user description
- Locate the issue in code
- Apply the minimal fix
- Check console via
read_consoleMCP — verify error is gone
What NOT To Do
- Don't refactor surrounding code
- Don't add defensive null checks everywhere — find why it's null
- Don't edit scene/prefab files directly — use MCP tools
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.
- 5d ago First seen · 42 lines · 35 tokens per session scan A 9e3b6112f39d
unity-fixer-lite is an agent published in the GitHub repository XeldarAlz/everything-claude-unity (21 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 306 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
verifying-worker-output
What a coordinator does after a worker reports succeeded. Dispatching workers and the report contract they follow live in the rove skill (.claude/skills/kobe/SKILL.md); this page starts where that ends — succeeded is a claim, not a verification. Every rule here was paid for in one night of verifying 26 worker PRs; the…
plan-chunks-agent
Use this agent for autonomous story planning — deep codebase research + detailed chunk breakdown in one focused pass. Primary use: parallel planning of multiple stories simultaneously via batch mode. Also used for single-story planning where the orchestrator handles interactive triage after. The orchestrator MUST…
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.…
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…