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/ui-click-debugnpx skills add yangfch3/Unity-MCP-Server --skill ui-click-debuggit clone --depth 1 https://github.com/yangfch3/Unity-MCP-ServerWhat 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.00054 | $0.00401 |
| Opus 5 | $0.00027 | $0.00200 |
| Sonnet 5 | $0.00011 | $0.00080 |
| Haiku 4.5 | $0.00005 | $0.00040 |
Grade A, and why
ui-click-debug 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
UI 点击问题排查
核心策略
优先执行运行时射线检测，一次 MCP 调用定位问题，避免逐层 Inspector 排查。
执行流程
Step 1: 获取目标节点
调用 editor_getSelection 获取用户选中的 UI 节点路径。
Step 2: 编写并执行射线检测代码
使用 code_executeImmediate 执行检测代码。需结合项目仓库和 PlayMode 实时情况即时编写，伪代码逻辑：
1. 通过路径/名称找到目标 GameObject
2. 获取其 RectTransform 世界坐标 → 转换为屏幕坐标
3. 构造 PointerEventData，调用 EventSystem.RaycastAll
4. 遍历命中结果，输出每个对象的：
- 完整路径
- sortingOrder / depth
- 是否为目标节点
5. 判断 results[0] 是否为目标，若不是则输出遮挡警告
Step 3: 分析日志结果
[0]不是目标 → 被遮挡，报告遮挡者- 目标不在列表 → 检查 RaycastTarget、CanvasGroup、激活状态
- 目标是
[0]→ 检查 Button.interactable、事件绑定
Step 4: 输出结论
- 问题原因：一句话
- 遮挡者：路径 + sortingOrder（如适用）
- 修复建议：一句话
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.
- 2d ago First seen · 43 lines · 54 tokens per session scan A 2981da134940
ui-click-debug is a skill published in the GitHub repository yangfch3/Unity-MCP-Server (6 stars, last pushed 8d ago), licensed MIT. It adds 54 tokens to every session and 401 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-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-logging
Reviews and improves Debug.Log usage in Unity C# projects following structured logging principles: context tags, severity contracts, boundary-based placement, and criticality tiers. Detects common antipatterns (naked Debug.Log, logging in Update, stringly-typed errors), adds missing logs at system/state/error/external…
jahro-migration
Analyzes existing debug systems (IMGUI menus, custom loggers, cheat frameworks, performance HUDs) and generates incremental migration plans to Jahro equivalents. Use when the user wants to replace a custom debug UI, migrate from an existing console or cheat system, switch to Jahro, or has OnGUI debug code they want to…
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.