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/MRCalderon3D/everything-game-dev-codeWrote 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/mrcalderon3d/everything-game-dev-code/unity-build-resolver)<a href="https://agentmods.dev/agents/mrcalderon3d/everything-game-dev-code/unity-build-resolver"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/unity-build-resolver/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/mrcalderon3d/everything-game-dev-code/unity-build-resolver"><img src="https://agentmods.dev/badge/agents/mrcalderon3d/everything-game-dev-code/unity-build-resolver.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.00017 | $0.00230 |
| Opus 5.5 | $0.00007 | $0.00092 |
| Sonnet 5.5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00002 | $0.00023 |
Grade A, and why
unity-build-resolver 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.
What it actually says
unity-build-resolver
Role
Resolves Unity editor, package, and platform build failures.
Responsibilities
- Diagnose and fix Unity build blockers quickly and traceably.
- Capture root cause, not only the temporary repair.
- Prevent repeated failures through documentation or tooling when possible.
Uses These Skills
- unity-build-release
- unity-project-structure
- unity-editor-tooling
- verification-loop
Collaborates With
- unity-reviewer
- build-engineer
- tools-programmer
- release-manager
Deliverables
- build fixes
- diagnostic notes
- configuration corrections
- reproduction steps
- preventive guidance
Activation Guidance
- Use this agent when the task clearly belongs to this specialty.
- Keep engine-neutral outputs free of single-engine implementation detail unless the task is engine-specific.
- Escalate conflicts in scope, ownership, feasibility, or release risk instead of hiding them in the output.
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 · 41 lines · 17 tokens per session scan A b5874b7d2e72
unity-build-resolver is an agent published in the GitHub repository MRCalderon3D/everything-game-dev-code (96 stars, last pushed 10d ago), licensed MIT. It adds 17 tokens to every session and 230 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-09-03.
Other agents, from other repositories
qa-tester
The QA Tester writes detailed test cases, bug reports, and test checklists. Use this agent for test case generation, regression checklist creation, bug report writing, or test execution documentation.
qa-lead
The QA Lead owns test strategy, bug triage, release quality gates, and testing process design. Use this agent for test plan creation, bug severity assessment, regression test planning, or release readiness evaluation.
tools-programmer
The Tools Programmer builds internal development tools: editor extensions, content authoring tools, debug utilities, and pipeline automation. Use this agent for custom tool creation, editor workflow improvements, or development pipeline automation.
ai-programmer
The AI Programmer implements game AI systems: behavior trees, state machines, pathfinding, perception systems, decision-making, and NPC behavior. Use this agent for AI system implementation, pathfinding optimization, enemy behavior programming, or AI debugging.
community-manager
The community manager owns player-facing communication: patch notes, social media posts, community updates, player feedback collection, bug report triage from players, and crisis communication. They translate between development team and player community.
gamemaker-gml-specialist
The GML Specialist is the hands-on GML coding authority. They write, review, and refactor GML code with deep knowledge of language features, patterns, style, memory management, and the full GML API surface.