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 skills add IdoCohen560/claude-unity-game-studio --skill uw-unity-debugginggit clone --depth 1 https://github.com/IdoCohen560/claude-unity-game-studioWrote 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/idocohen560/claude-unity-game-studio/uw-unity-debugging)<a href="https://agentmods.dev/skills/idocohen560/claude-unity-game-studio/uw-unity-debugging"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/uw-unity-debugging/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/skills/idocohen560/claude-unity-game-studio/uw-unity-debugging"><img src="https://agentmods.dev/badge/skills/idocohen560/claude-unity-game-studio/uw-unity-debugging.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.00116 | $0.01184 |
| Opus 5 | $0.00058 | $0.00592 |
| Sonnet 5 | $0.00023 | $0.00237 |
| Haiku 4.5 | $0.00012 | $0.00118 |
Grade A, and why
uw-unity-debugging 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 9d 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.
This is a copy
100% identical to uw-unity-debugging — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Debugging
4-phase debugging framework. Also generates the GameDebug wrapper class.
Before You Start
- Check if
GameDebug.csalready exists in the project (search forclass GameDebug). If not, generate it using the template below during project setup. - Read
docs/ProjectConfig.yaml -> mcp.unity_mcp— iftrue, useread_consoleto read Unity console output. - Read
docs/CODING_STANDARDS.mdfor async patterns — bugs in async code often involve missingCancellationTokenor unhandledOperationCanceledException.
4 Phases
Phase 1: Gather Evidence
- Read Unity console (
read_consolevia MCP or ask user for errors). - Reproduce — exact steps to trigger.
- Scope — single script, system interaction, or timing?
- Check
git log -5for recent changes.
Phase 2: Isolate
- Comment out systems to narrow the culprit.
- Add targeted
GameDebug.Logat decision points. - Check common causes:
- Execution order (
AwakevsStartvsOnEnable) - Null reference (destroyed object, unassigned field)
- Unity API called from background thread
- State not reset in
OnDisable/OnDestroy - Physics in
Updateinstead ofFixedUpdate
- Execution order (
Phase 3: Hypothesize & Test
- State: "I believe X happens because Y."
- Write a test proving/disproving the hypothesis.
- If test fails -> back to Phase 2.
Phase 4: Fix & Verify
- Implement minimal fix.
- Re-run the hypothesis test.
- Run full test suite for regressions.
- Clean up temp debug logs.
- Commit:
fix({scope}): {root cause description}
GameDebug Wrapper
Generate during project setup. Uses [Conditional("ENABLE_LOGS")] so all calls are stripped in release builds. Includes [CallerFilePath], [CallerMemberName], and [CallerLineNumber] for automatic context — no need to manually describe where a log came from.
using System.Diagnostics;
using System.Runtime.CompilerServices;
public enum LogTopic { General, Gameplay, Audio, UI, Network, Physics, AI }
public static class GameDebug
{
[Conditional("ENABLE_LOGS")]
public static void Log(
string message,
LogTopic topic = LogTopic.General,
[CallerFilePath] string file = "",
[CallerMemberName] string member = "",
[CallerLineNumber] int line = 0) =>
UnityEngine.Debug.Log(Format(topic, message, file, member, line));
[Conditional("ENABLE_LOGS")]
public static void LogWarning(
string message,
LogTopic topic = LogTopic.General,
[CallerFilePath] string file = "",
[CallerMemberName] string member = "",
[CallerLineNumber] int line = 0) =>
UnityEngine.Debug.LogWarning(Format(topic, message, file, member, line));
[Conditional("ENABLE_LOGS")]
public static void LogError(
string message,
LogTopic topic = LogTopic.General,
[CallerFilePath] string file = "",
[CallerMemberName] string member = "",
[CallerLineNumber] int line = 0) =>
UnityEngine.Debug.LogError(Format(topic, message, file, member, line));
private static string Format(
LogTopic topic, string msg, string file, string member, int line) {
var fileName = System.IO.Path.GetFileNameWithoutExtension(file);
return $"[{topic}] {fileName}.{member}:{line} — {msg}";
}
}
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.
- 9d ago First seen · 111 lines · 116 tokens per session scan A 036e08d58cf8
uw-unity-debugging is a skill published in the GitHub repository IdoCohen560/claude-unity-game-studio (19 stars, last pushed 2mo ago), licensed MIT. It adds 116 tokens to every session and 1,184 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to uw-unity-debugging, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
log-correlation
Correlates and troubleshoots logs across OS (Linux/macOS), AWS (CloudWatch, CloudTrail, ALB, Lambda), application (JSON, logfmt), and web servers (Nginx, Apache).
swarm
Run a multi-agent audit of a codebase by spawning specialized parallel subagents (security, performance, tests, architecture, dead-code), then synthesize their findings into a single prioritized action plan. Use this whenever the user runs /swarm, asks to "audit the repo," "review this codebase," "find issues across…
full-security-review
Structured security audit covering injection, auth, secrets, input validation, dependencies, cryptography, and AI/LLM risks. Produces severity-graded findings.
accessibility
Audits code for WCAG 2.2 AA compliance and provides design guidance for accessible components. Covers semantic HTML, ARIA, keyboard nav, contrast, focus management, and motion.
git-workflow
Enforces the release-branch Git model: scaffold feature branches, open PRs with review checks, cut releases with tags, and view workflow reference.
api-design
Designs REST, GraphQL, and gRPC APIs (OpenAPI/schema/proto output) and reviews existing APIs for consistency, best practices, and breaking change risks.