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/fix-bugnpx skills add nowsprinting/unity-coding-skills --skill fix-buggit 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.00086 | $0.02309 |
| Opus 5 | $0.00043 | $0.01154 |
| Sonnet 5 | $0.00017 | $0.00462 |
| Haiku 4.5 | $0.00009 | $0.00231 |
Grade A, and why
fix-bug 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Guide for diagnosing and fixing bugs. This skill defines a test-first debugging workflow: reproduce the bug with a failing test, diagnose the root cause, then fix it.
Mode Check
This skill must be used outside plan mode. Before doing anything else, check the current mode:
ExitPlanModeis NOT in the deferred tools list (i.e., directly callable) → in plan mode → stop immediately and tell the user:"This skill (
/fix-bug) must be used outside plan mode. Please exit plan mode first."ExitPlanModeis in the deferred tools list → not in plan mode → proceed.
Workflow
Recording implementation notes: Notes for this run go in /tmp/fix-bug-notes-$CLAUDE_CODE_SESSION_ID.md. Immediately before your first append in this run — and only then — delete that file if it exists (usually it will not), so this run starts from an empty one: the session id is shared by every /fix-bug run in the session, so an earlier run abandoned before Step 9 would otherwise leak its notes into this one. Never delete it again afterwards, including when Step 3 sends you back to Step 1 or Step 2; those loops are part of the same run and their notes must survive.
While working through Steps 1-8, whenever one of the following occurs, immediately append a line to that file — do not wait until the end to reconstruct these from memory:
- The confirmed Condition / Expected / Actual differs from what the user first reported, or the documentation conflicted with the report and you resolved which is correct → Bug report clarifications
- You established — or later revised — which line(s) or logic are responsible and why they misbehave, including when the fix actually applied differs from the one formulated in Step 5 → Root cause
- You investigated a suspected cause, code path, or reproduction approach and eliminated it → Ruled out
- You considered alternatives and chose one, and why → Tradeoffs
- You modified or deleted test code that was already committed, and why → Test changes
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 · 177 lines · 86 tokens per session scan A 613d4f527918
fix-bug is a skill published in the GitHub repository nowsprinting/unity-coding-skills (19 stars, last pushed 2d ago), licensed Unlicense. It adds 86 tokens to every session and 2,309 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-pipeline
Drive this repo's running Unity Editor from the shell via the official unity CLI and the com.unity.pipeline package — recompile/test loop, C# eval, console logs, Game/Scene screenshots, the srgate SerializeReference check, and authoring new [CliCommand] commands. Use whenever a task needs to compile, test, inspect, or…
editor-media-capture
Shoot Unity Editor screenshots and GIFs for this package's documentation without the user touching Unity — floating Inspectors, TypeSelectorWindow dropdowns, prefab-mode states, and ffmpeg GIF assembly. Use when a task asks for docs media (PNG/GIF) of editor UI under Documentation/Images, or when scripting…
sync-readmes
Verify and update Aspid.FastTools README files against the actual codebase — namespaces, public API, CreateAssetMenu paths — keeping EN/RU and root/Documentation copies in sync.
build-analyzer
Build the Roslyn analyzer and deploy the resulting DLL into the Unity package.
build-generator
Build Roslyn source generators and deploy the resulting DLL into the Unity package.
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…