agentmods.dev

unity_code_mcp CLAUDE.md

Project instructions for a Rust-based MCP server that connects AI assistants with the Unity game editor, including log access and test management.

In plain words
What is it for?
Use them when developing or reviewing this Unity integration, especially its handling of editor reloads, logs, and tests.
Why use it?
They give coding agents the project's purpose, architecture, technologies, and development rules when working on the server.

Instructions file

11 1mo ago A scan 550 tokens original MIT
View the source file hackerzhuli/unity_code_mcp
Install

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.

agentmods
npx agentmods add instructions/hackerzhuli/unity_code_mcp/claude-md
Clone the repo
git clone --depth 1 https://github.com/hackerzhuli/unity_code_mcp
Per session 550 This file is loaded in full into every session.
When invoked 550 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00550 $0.00550
Opus 5 $0.00275 $0.00275
Sonnet 5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

Measured 2d ago against content hash ad58bfb1f7f3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

unity_code_mcp CLAUDE.md 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 2d 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.

CLAUDE.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Unity Code MCP Server - Project Rules

Project Purpose

This project aims to create a reliable Model Context Protocol (MCP) server that enables AI assistants to communicate effectively with Unity Editor. The primary motivation is to address the limitations of existing Unity MCP servers, particularly their inability to handle Unity's domain reload functionality, which causes Unity Editor components to become unavailable.

Core Objectives

  • Build a robust MCP server that survives Unity domain reloads
  • Provide essential Unity integration features:
    • Retrieve Unity logs
    • Execute and manage Unity tests
  • Serve as a component for the Unity Code Pro VS Code extension
  • Enable seamless AI-Unity Editor communication

Tech Stack

Core Technologies

  • Language: Rust
  • MCP Framework: rmcp (core dependency)
  • Async Runtime: Tokio (implicit dependency via rmcp)
  • Architecture: Single-threaded async to minimize complexity

Dependencies

  • rmcp: Primary MCP implementation
  • tokio: Async I/O runtime

Development Guidelines

Architecture Principles

  1. Simplicity First: Use single-threaded async architecture to avoid unnecessary complexity

Code Standards

  1. Rust Best Practices:

    • Follow Rust naming conventions
    • Maintain comprehensive error handling

  2. Async Programming:

    • Leverage Tokio's single-threaded runtime
    • Use async/await patterns consistently
    • Avoid blocking operations in async contexts

  3. MCP Protocol Compliance:

    • Implement MCP tools according to specification
    • Ensure proper error handling and response formatting
    • Maintain protocol version compatibility

Project Structure

  • Keep the codebase minimal and focused
  • Organize code by functionality (logs, tests, core MCP handling)
  • Maintain clear separation between Unity communication and MCP protocol handling

Testing Strategy

  • Unit tests for most functionality
  • A real (but minimal) Unity project is embedded in UnityProject for running related tests (that doesn't require a running Unity Editor instance, just need files, including Unity generated files)
  • Don't create examples binaries(for testing or any other reason), only do unit tests for testing
  • Our tests can take a long time to run(30-60 seconds), so avoid running all tests when possible, focus testing individual modules that we're actively working on.

Read the full file on GitHub · 67 lines

Changes

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.

  1. 2d ago First seen · 67 lines · 550 tokens per session scan A ad58bfb1f7f3

Subscribe to this mod's changes

unity_code_mcp CLAUDE.md is an instructions file published in the GitHub repository hackerzhuli/unity_code_mcp (11 stars, last pushed 1mo ago), licensed MIT. It adds 550 tokens to every session, about $0.0028 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.

Game developmentLanguagesTestingaigamemcpunity
Related

Other instructions, from other repositories

Unity-MCP copilot-instructions.md

Instructions for IvanMurzak/Unity-MCP, covering project guidelines, critical rules, no c# reflection for private access, code review and code style.

IvanMurzak/Unity-MCP · 895 tokens

mcp-unity AGENTS.md

Instructions for CoderGamester/mcp-unity, covering mcp unity — ai agent guide (mcp package), purpose (what this repo is), how it works (high-level data flow), key defaults & invariants and repo layout (where to change what).

CoderGamester/mcp-unity · 2,498 tokens

core CLAUDE.md

Instructions for ReactUnity/core, covering claude.md, what this repo is, two package universes, pnpm workspace membership and commands.

ReactUnity/core · 6,014 tokens

Unity-MCP CLAUDE.md

Instructions for IvanMurzak/Unity-MCP, covering claude.md, what this is, build / run, project constitution and find detail in.

IvanMurzak/Unity-MCP · 503 tokens

unity-cli-loop AGENTS.md

AGENTS.md instructions for hatayama/unity-cli-loop, covering architecture overview, repository map, cli / unity package compatibility, project runner pin and generated skill files.

hatayama/unity-cli-loop · 3,014 tokens

core AGENTS.md

Instructions for ReactUnity/core, covering release workflow, write changelog files, example, fix button hover state and package references.

ReactUnity/core · 245 tokens