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/nowsprinting/unity-coding-skills/resolve-diagnosticsnpx skills add nowsprinting/unity-coding-skills --skill resolve-diagnosticsgit clone --depth 1 https://github.com/nowsprinting/unity-coding-skillsWhat 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.00084 | $0.01384 |
| Opus 5 | $0.00042 | $0.00692 |
| Sonnet 5 | $0.00017 | $0.00277 |
| Haiku 4.5 | $0.00008 | $0.00138 |
Grade A, and why
resolve-diagnostics 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resolves IDE diagnostics at the warning or higher severity level for the given files, reformats
them to the solution's code style, then runs the tests.
Input
One or more file path arguments. Resolve them to a concrete set of files, then:
- Keep only
.csfiles that belong to the current Unity solution — they are the only ones that carry IDE diagnostics, andreformat_filerequires solution membership. - Drop everything else (docs,
.meta,.asmdef, assets, files outside the solution). - Normalize the remaining paths to project/solution-root-relative form, once, up front —
lint_files,get_file_problems, andreformat_fileall expect that form.
If no path argument is given, use AskUserQuestion to ask the user for the targets. Do not derive
targets from git status — that would silently widen the scope beyond what was requested.
If no files remain after filtering, stop and report that — there is nothing to resolve.
Workflow
Step 1: Load the Coding Guide
- Load the
code-writing-guideskill — do not rely on automatic skill triggering. Every fix applied in Step 2 must follow it. - Read its
resources/diagnostics-review-feedback.mdnow, before collecting any diagnostics in Step 2 — do not wait for its## Resourcesbullet to be reached incidentally; a diagnostic fix decision must never be made before this file has been read in this run.
Never leave a warning-or-higher diagnostic unaddressed — each one is either fixed or explicitly
suppressed per the criteria just read.
Step 2: Resolve Diagnostics
Resolve diagnostics at the warning or higher severity level, collecting them for all resolved
files via lint_files rather than one file at a time. By default the tools also return
suggestion- and hint-level results — those are out of scope, with one exception: a
suggestion-level diagnostic related to performance (execution speed, memory allocation, boxing,
etc.) should be considered for fixing too, though it never requires suppression when declined.
Both lint_files and its fallback get_file_problems require Rider 2026.2 or later.
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 · 113 lines · 84 tokens per session scan A fe70f1f0c6ec
resolve-diagnostics is a skill published in the GitHub repository nowsprinting/unity-coding-skills (19 stars, last pushed 2d ago), licensed Unlicense. It adds 84 tokens to every session and 1,384 once invoked, about $0.0004 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.
Other skills, from other repositories
unity
Compile, test, and drive Unity for this repo's C# packages (unity/core, jint, quickjs, clearscript) and the two Unity projects (tests/, kitchen-sink/). Use when a change touches C# under unity/, when Unity test results are needed, when a rendering snapshot has to be checked or regenerated, or when the app has to be…
uloop-execute-dynamic-code
Execute C# with Unity APIs when existing uloop tools cannot inspect or edit enough. Use for reachable scene/component state, scene/prefab/menu automation, and PlayMode checks.
uloop-simulate-mouse-input
Simulate Mouse.current input in PlayMode through Unity Input System. Use for gameplay mouse clicks, long-press (LongPress), movement delta (MoveDelta/SmoothDelta), or scroll. Use --dry-run to check what a Game View coordinate hits in 3D physics before clicking (works in EditMode; no Input System required). Use…
uloop-simulate-mouse-ui
Simulate PlayMode EventSystem UI mouse actions using screen coordinates. Use for UI clicks, long-presses, or drags from annotated screenshots.
uloop-pause-point
Pauses Unity playback at any source file:line without editing code or recompiling, and returns a snapshot of the locals, parameters, and instance fields at that exact frame. Use for bug investigation, PlayMode/E2E verification, checking variable values at a specific frame, or confirming that a code path executed.
uloop-screenshot
Capture Unity Editor windows or Game View rendering as PNG. Use for visual checks, debugging, documentation, or annotated UI element coordinates.