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/nth5693/gemini-kit/debugnpx skills add nth5693/gemini-kit --skill debuggit clone --depth 1 https://github.com/nth5693/gemini-kitWhat 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.00013 | $0.00292 |
| Opus 5 | $0.00006 | $0.00146 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- debug — 100% identical, 0 lines differ
What it actually says
Debug Skill
Overview
Don't guess; verify. This skill guides you through the systematic process of identifying, reproducing, and fixing bugs.
When To Use
- Users report a bug
- You encounter an unexpected error
- Tests are failing inexplicably
Instrumentation
# Log usage when using this skill
./scripts/log-skill.sh "debug" "manual" "$$"
What do you want to do?
- Reproduce an issue →
workflows/reproduce-issue.md - Find Root Cause →
workflows/root-cause-analysis.md - Create Bug Report →
templates/bug-report.template.md - Research Error Messages →
references/common-errors.md
The Golden Rule of Debugging
"If you haven't reproduced it, you haven't fixed it."
Always implement a reproduction case (test or script) BEFORE attempting a fix. Highly recommended to use the template at docs/templates/repro-script-template.sh and store artifacts in scripts/repro/.
[!NOTE] No top-level
debug/folder exists. Useskills/debug/for guidance andscripts/repro/for artifacts.
What ships with it
2 files 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 · 41 lines · 13 tokens per session scan A 3562e9bb26b8
debug is a skill published in the GitHub repository nth5693/gemini-kit (375 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 292 once invoked, about $0.0001 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
triage-issue
Investigate a reported bug to root cause, then emit a TDD-shaped fix plan as an issue artifact. Trigger when the user reports a bug, says "triage", asks for issue investigation, or wants a fix plan before code changes.
minimalist-general
Subtraction-first thinking for non-coding tasks: writing, planning, research, summarizing, decision-making, or any request that isn't producing code. Same discipline as the minimalist coding skill — question whether the ask is even needed, reuse what already exists, do the smallest thing that fully answers it …
minimalist
Subtraction-first engineering for any coding task. Use when writing, fixing, refactoring, reviewing, or designing code; when choosing dependencies; or whenever the user asks for minimalist, less code, simplest thing, YAGNI, or complains about bloat. Prefer deletion, existing code, stdlib, and native platform features…
minimalist-audit
Audit a codebase or directory for deletion candidates: dead code, unused dependencies, single-use abstractions, config that never varies, and duplicated helpers. Use when the user says "minimalist audit" or asks what can be deleted from a project.
minimalist-gain
Report what minimalist actually measured in this session or project — LOC avoided, scope rejected, dependencies declined. Use when the user says "minimalist gain", "what did you save", or asks for the savings report.
minimalist-review
Review code, a diff, or a PR strictly for bloat: unrequested abstractions, dead scope, dependency creep, symptom-patching, and drive-by changes. Use when the user says "minimalist review", asks "is this over-engineered?", or wants a leanness review of a change.