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/dojogenesis/mcp/debuggingnpx skills add DojoGenesis/mcp --skill debugginggit clone --depth 1 https://github.com/DojoGenesis/mcpWhat 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.00052 | $0.03061 |
| Opus 5 | $0.00026 | $0.01530 |
| Sonnet 5 | $0.00010 | $0.00612 |
| Haiku 4.5 | $0.00005 | $0.00306 |
Grade A, and why
debugging-troubleshooting 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 yesterday.
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 — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging & Troubleshooting Skill
Version: 1.2 Author: Tres Pies Design Purpose: Systematic debugging and troubleshooting that finds root causes, not just patches symptoms.
I. Philosophy: Systematic Diagnosis
Debugging is systematic investigation, not random guessing. One change at a time, test, observe, learn. Intuition is useful but methodology prevents rabbit holes.
Core principle: You can't fix what you can't reproduce.
II. When to Use This Skill
- Code behaves unexpectedly (errors, crashes, wrong output)
- Performance degradation (slow queries, long build times)
- Data inconsistency (state out of sync)
- Integration failure (API returns errors, sync breaks)
- Feature not working as expected (UI bug, logic error)
III. The 7-Step Debugging Workflow
Always follow these steps in order. Never jump to fixing without reproducing.
Step 1: Reproduce
Can the user reproduce the problem consistently?
- Identify exact steps to trigger the issue
- Run reproduction 3+ times
- Note if it happens every time or intermittently
- If intermittent, identify patterns (time of day, data size, user count, load)
If you can't reproduce it, you can't fix it. Invest time here.
Information Gathering Template:
## Debug: [Issue Title]
**Gathered:** [Date/Time]
**Error Message:**
[Exact error text]
**Stack Trace:**
[Copy relevant portion]
**Logs:**
[Key log lines with timestamps]
**Context:**
- What triggered the issue:
- Recent changes:
- Environment:
- Node: [version]
- Database: [version]
- OS: [platform]
**Expected Behavior:**
[What should happen]
**Actual Behavior:**
[What actually happened]
Step 2: Isolate
Narrow the scope. Which component, file, function, or line?
Bisection strategy: When many variables exist, use binary search to narrow down:
- Split the system in half
- Test each half independently
- The half that fails contains the bug
- Repeat until you've isolated the specific component
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.
- yesterday First seen · 408 lines · 52 tokens per session scan A 799f8151373b
debugging-troubleshooting is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 52 tokens to every session and 3,061 once invoked, about $0.0003 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-31.
Other skills, from other repositories
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.
sq-actions-dependabot
Reviews and merges Dependabot pull requests for GitHub Actions (the github-actions ecosystem) that bump uses: pins in .github/workflows/. Use for Dependabot githubactions PRs (branches like dependabot/githubactions/...), not go.mod or site/ Bun PRs.
jwx-companion-bulk
Apply bulk operations across all jwx companion modules. Args.
readme-generate
從原始碼分析自動生成雙語 README。當使用者請求為專案建立 README、需要從程式碼庫生成 README.md（英文）和 README.zh.md（中文）、或希望為其函式庫/套件建立一致的多語言文件時使用。.
gograph
Go repository intelligence for Claude Code. Use when reading, navigating, editing, reviewing, or refactoring a Go codebase. Exposes 64 query, analysis, and workflow capabilities through the local gograph MCP server, including bounded first-call exploration, AST-aware call graphs, blast-radius analysis, impact, and…