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 nowsprinting/unity-coding-skills --skill fix-buggit clone --depth 1 https://github.com/nowsprinting/unity-coding-skillsWrote 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/nowsprinting/unity-coding-skills/fix-bug)<a href="https://agentmods.dev/skills/nowsprinting/unity-coding-skills/fix-bug"><img src="https://agentmods.dev/badge/skills/nowsprinting/unity-coding-skills/fix-bug/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/nowsprinting/unity-coding-skills/fix-bug"><img src="https://agentmods.dev/badge/skills/nowsprinting/unity-coding-skills/fix-bug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.02322 |
| Opus 5.5 | $0.00034 | $0.00929 |
| Sonnet 5.5 | $0.00017 | $0.00464 |
| Haiku 4.5 | $0.00009 | $0.00232 |
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 today.
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 <scratchpad>/implementation-notes.md, where <scratchpad> is the scratchpad directory listed in your system prompt (write its absolute path literally). 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: every /fix-bug, /refine-tests, and plan-file run in the session shares this file, so an earlier run abandoned before its Implementation Notes step 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.
- today Changed 37287d8ad53b
- 24d ago Changed a9f2b653e77c
- 1mo 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 (20 stars, last pushed today), licensed Unlicense. It adds 86 tokens to every session and 2,322 once invoked, about $0.0003 per session on Opus 5.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
dotnet-test
This skill should be used when running .NET tests selectively with a build-first, test-targeted workflow. Use it for running tests with xUnit focus.
investigate
A structured root-cause investigation method for software bugs. It moves from history and reproduction through tested hypotheses, a focused fix, verification, and a report.
asp-ft-release
Release an Aspid.FastTools version end to end. Phase 1 opens the release PR (CHANGELOG section, version files, local tests, Unity EditMode); the user merges it. Phase 2 pushes the v tag after the user's yes and checks what the Release workflow published. The version alone picks the channel. - /asp-ft-release…
dart-flutter-equatable-engineering
Design, implement, review, debug, test, migrate, and optimize value equality in production Dart and Flutter code using Equatable or appropriate alternatives. Use this skill whenever work involves Equatable, props, immutable Bloc/Cubit states or events, equality bugs, suppressed state emissions, lists/sets/maps in…
Vitest Mock Isolation Review
Detects Vitest test-isolation hazards: unrestored vi.spyOn/vi.mock without afterEach cleanup or restoreMocks config, un-awaited resolves/rejects assertions, and shared mutable module state across tests.
test-fix-loop
This skill should be used when autonomously iterating on test failures: runs the suite, diagnoses, applies minimal fixes, re-runs with checkpoint commit isolation until all tests pass.