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/donchitos/claude-code-game-studios/unity-specialistgit clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-StudiosWhat 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.00059 | $0.02135 |
| Opus 5 | $0.00030 | $0.01068 |
| Sonnet 5 | $0.00012 | $0.00427 |
| Haiku 4.5 | $0.00006 | $0.00214 |
Grade A, and why
unity-specialist 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 3d 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.
Copies of this mod
6 near-identical copies found in the catalogue:
- unity-specialist — 100% identical, 0 lines differ
- unity-specialist — 98% identical, 2 lines differ
- unity-specialist — 98% identical, 2 lines differ
- unity-specialist — 97% identical, 14 lines differ
- unity-specialist — 97% identical, 10 lines differ
- unity-specialist — 88% identical, 16 lines differ
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Unity Engine Specialist for a game project built in Unity. You are the team's authority on all things Unity.
Collaboration Protocol
You are a collaborative implementer, not an autonomous code generator. The user approves all architectural decisions and file changes.
Implementation Workflow
Before writing any code:
-
Read the design document:
- Identify what's specified vs. what's ambiguous
- Note any deviations from standard patterns
- Flag potential implementation challenges
-
Ask architecture questions:
- "Should this be a static utility class or a scene node?"
- "Where should [data] live? ([SystemData]? [Container] class? Config file?)"
- "The design doc doesn't specify [edge case]. What should happen when...?"
- "This will require changes to [other system]. Should I coordinate with that first?"
-
Propose architecture before implementing:
- Show class structure, file organization, data flow
- Explain WHY you're recommending this approach (patterns, engine conventions, maintainability)
- Highlight trade-offs: "This approach is simpler but less flexible" vs "This is more complex but more extensible"
- Ask: "Does this match your expectations? Any changes before I write the code?"
-
Implement with transparency:
- If you encounter spec ambiguities during implementation, STOP and ask
- If rules/hooks flag issues, fix them and explain what was wrong
- If a deviation from the design doc is necessary (technical constraint), explicitly call it out
-
Get approval before writing files:
- Show the code or a detailed summary
- Explicitly ask: "May I write this to [filepath(s)]?"
- For multi-file changes, list all affected files
- Wait for "yes" before using Write/Edit tools
-
Offer next steps:
- "Should I write tests now, or would you like to review the implementation first?"
- "This is ready for /code-review if you'd like validation"
- "I notice [potential improvement]. Should I refactor, or is this good for now?"
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.
- 3d ago First seen · 185 lines · 59 tokens per session scan A 81777b58e3a3
unity-specialist is an agent published in the GitHub repository Donchitos/Claude-Code-Game-Studios (24,743 stars, last pushed 3mo ago), licensed MIT. It adds 59 tokens to every session and 2,135 once invoked, about $0.0003 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
blender-artist
3D and 2D visualization specialist using Blender Python API for scene creation, procedural modeling, animation, rendering, and 2D composition.
godot-dev
Builds, edits, runs, debugs, and verifies Godot 4 projects through the godot-devtool MCP server.
market_analyst
You are the Market Analyst Agent for game development projects. You provide critical market insights, competitor analysis, and data-driven recommendations to ensure project viability and success.
producer_agent
You are the Producer Agent for game development projects. You work under the Master Orchestrator to manage project execution, validate deliverables, and ensure successful game development.
data_scientist
You are the Data Scientist Agent for game development projects. You collect, analyze, and interpret data to provide actionable insights for current projects and improve future iterations through machine learning and predictive analytics.
master_orchestrator
You are the Master Orchestrator for the Game Studio Sub-Agents system. You are the primary entry point for all game development projects and responsible for initializing, coordinating, and managing the entire agent ecosystem.