Borrowing it
Nothing to install: this file belongs to yangfch3/Unity-MCP-Server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yangfch3/Unity-MCP-Server/main/.kiro/steering/readme-tool-docs.mdgit clone --depth 1 https://github.com/yangfch3/Unity-MCP-ServerWrote 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/instructions/yangfch3/unity-mcp-server/readme-tool-docs)<a href="https://agentmods.dev/instructions/yangfch3/unity-mcp-server/readme-tool-docs"><img src="https://agentmods.dev/badge/instructions/yangfch3/unity-mcp-server/readme-tool-docs/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/instructions/yangfch3/unity-mcp-server/readme-tool-docs"><img src="https://agentmods.dev/badge/instructions/yangfch3/unity-mcp-server/readme-tool-docs.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.00403 | $0.00403 |
| Opus 5 | $0.00201 | $0.00201 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00040 | $0.00040 |
Grade A, and why
Unity-MCP-Server readme-tool-docs.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.
What it actually says
README Tool Documentation Sync
When adding a new IMcpTool implementation, you MUST also update the tool tables in both README.md and README_EN.md, as well as the detailed docs in Docs/TOOLS.md and Docs/TOOLS_EN.md.
Editor Tools Sub-Group Classification
The "Editor 工具" / "Editor Tools" section uses four sub-groups (five-level headings):
| Sub-Group | Rule |
|---|---|
| Query | Read-only tools that retrieve scene, object, or project information (e.g., editor_get*, editor_find*) |
| Mutation | Tools that create, modify, or delete GameObjects, components, or serialized fields (e.g., editor_add*, editor_set*, editor_delete*, editor_remove*, editor_reparent*, editor_select*) |
| Project | Cross-scene operations like menu execution and PlayMode control (e.g., menu_*, playmode_*) |
| Asset | Asset management operations on the Assets directory (e.g., asset_*) |
Rules
- Place the new tool in the correct sub-group table based on the classification above.
- Add entries to BOTH
README.md(Chinese) andREADME_EN.md(English) with matching descriptions. - Add detailed parameter documentation to BOTH
Docs/TOOLS.md(Chinese) andDocs/TOOLS_EN.md(English) under the correct sub-group heading. - If the new tool does not fit any existing sub-group, create a new sub-group with a five-level heading in both READMEs and a three-level heading in both Docs files.
- Keep tools within each sub-group sorted logically (query tools by scope, mutation tools by operation type).
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.
- 2d ago First seen · 28 lines · 403 tokens per session scan A dbabe869a5c8
Unity-MCP-Server readme-tool-docs.md is an instructions file published in the GitHub repository yangfch3/Unity-MCP-Server (6 stars, last pushed 2d ago), licensed MIT. It adds 403 tokens to every session, about $0.0020 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-09-10.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).