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 skills/yangfch3/unity-mcp-server/error-diagnosisnpx skills add yangfch3/Unity-MCP-Server --skill error-diagnosisgit 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/skills/yangfch3/unity-mcp-server/error-diagnosis)<a href="https://agentmods.dev/skills/yangfch3/unity-mcp-server/error-diagnosis"><img src="https://agentmods.dev/badge/skills/yangfch3/unity-mcp-server/error-diagnosis.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.00124 | $0.00578 |
| Opus 5 | $0.00062 | $0.00289 |
| Sonnet 5 | $0.00025 | $0.00116 |
| Haiku 4.5 | $0.00012 | $0.00058 |
Grade A, and why
error-diagnosis 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 4d 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
报错排查 Skill
从 Unity Console 获取错误日志，结合前序上下文日志和仓库代码，定位报错原因并给出修复建议。
执行流程
Step 1: 获取 Error 日志
调用 console_getLogs(level: "Error")，获取最近的错误日志。
- 如果没有 Error，告知用户控制台无错误，流程结束。
- 记录每条 Error 的
index、message、stackTrace，用于后续步骤。
Step 2: 获取前序上下文日志
根据最早一条 Error 的 index，调用 console_getLogs(beforeIndex: <errorIndex>) 获取报错前的上下文日志。
- 默认获取 15 条
- 用户提到"仔细排查"或"详细排查"时，扩展到 30 条
Step 3: 结合代码定位原因
根据 Error 的 stackTrace 和 message：
- 提取关键信息：报错模块、文件路径、行号、关键变量/标识符
- 在仓库中搜索相关代码（grep 关键标识符、读取报错文件的上下文代码）
- 结合前序日志的时间线，还原报错发生的完整流程
Step 4: 输出结论
用简洁的格式输出，禁止大段分析过程：
- 报错流程：用编号列表简述从触发到报错的关键步骤（每步一句话）
- 报错原因：一两句话直指根因
- 修复建议：如果是测试代码的预期行为，说明无需修复；否则给出简洁的修复方向
注意事项
- 输出要简洁凝练，不要罗列原始日志或大段代码
- 如果多条 Error 属于同一问题（如连续的 stackTrace 补充信息），合并分析
- 前序日志中的 Warning 也要关注，可能包含问题线索
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 52 lines · 124 tokens per session scan A 783920b6dc67
error-diagnosis is a skill published in the GitHub repository yangfch3/Unity-MCP-Server (6 stars, last pushed 2d ago), licensed MIT. It adds 124 tokens to every session and 578 once invoked, about $0.0006 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-31.
Other skills, from other repositories
dotcraft-unity
Use when dotcraft-unity MCP or unityexecutecsharp is available, or when the user asks to inspect, automate, capture, or debug Unity Editor state, scenes, assets, Console logs, or GameView output. Provides background-first Unity Editor automation rules.
jahro-troubleshooting
Diagnoses common Jahro issues using decision trees: commands not appearing, watcher not updating, console not opening, snapshots failing, launch button missing. Use when the user reports something not working, missing, broken, or unexpected with Jahro, or when generated Jahro code doesn't behave as expected.
jahro-commands
Analyzes C# classes and generates [JahroCommand] attributes with correct syntax, RegisterObject patterns, and group organization. Use when the user wants to add runtime commands, cheats, or debug actions to Unity classes, or mentions JahroCommand, console commands, runtime cheats, or debug actions.
jahro-watcher
Analyzes C# fields and properties and generates [JahroWatch] attributes with groups and performance-safe patterns. Use when the user wants to monitor variables at runtime, add watchers, track game state, replace Debug.Log polling, or mentions JahroWatch, real-time inspection, or variable monitoring.
jahro-production
Configures Jahro lifecycle controls for safe production deployment including JAHRODISABLE, auto-disable, and build validation. Use when the user mentions production builds, release builds, disabling Jahro, shipping, CI/CD, lifecycle controls, or production safety.
jahro-setup
Detects Jahro in Unity projects and guides installation, API key configuration, and feature overview. Use when the user mentions Jahro setup, installation, getting started, debug console, or asks what Jahro can do. Also triggers when no Jahro references are found in a Unity project and the user asks about debugging.