debug

debug is a skill for Claude Code, Codex from DongDuong2001/pudo-code-system. It costs 0 tokens per session (462 once invoked), scanned A, original, MIT.

A systematic guide for diagnosing bugs, error messages, and unexpected software behavior.

In plain words
What is it for?
Use it to analyze an error trace, narrow down one or two possible root causes, and determine the code changes needed to fix the problem.
Why use it?
It helps replace guesswork with a comparison of expected and actual behavior, likely causes, and evidence from the relevant code and logs.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to analyze an error trace, narrow down one or two possible root causes, and determine the code changes needed to fix the problem.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dongduong2001/pudo-code-system/debug
Install

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.

Any agent
npx skills add DongDuong2001/pudo-code-system --skill debug
Clone the repo
git clone --depth 1 https://github.com/DongDuong2001/pudo-code-system

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for debug

README.md
[![agentmods](https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/debug/github.svg)](https://agentmods.dev/skills/dongduong2001/pudo-code-system/debug)
Your own site
<a href="https://agentmods.dev/skills/dongduong2001/pudo-code-system/debug"><img src="https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/debug/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.

agentmods 80×15 button for debug

Your own site · 80×15
<a href="https://agentmods.dev/skills/dongduong2001/pudo-code-system/debug"><img src="https://agentmods.dev/badge/skills/dongduong2001/pudo-code-system/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 462 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00462
Opus 5.5 $0.00000 $0.00185
Sonnet 5.5 $0.00000 $0.00092
Haiku 4.5 $0.00000 $0.00046

Measured 1mo ago against content hash 3e08da3bb95d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/debug/SKILL.md · 54 lines

How it starts

The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Troubleshooting & Debugging Skill

Skill, Debugging, SRE, Bug Fixing

Context

Use this prompt when you are facing a bug, error trace, or unexpected behavior. This skill forces the AI to act as a troubleshooter, analyzing root causes systematically rather than just guessing solutions.

Variables

  • {{error_message}}: The exact error trace or log output.
  • {{behavior_description}}: What you expected to happen vs what actually happened.
  • {{context_code}}: The snippet of code where the error is occurring.

Prompt

Adopt the persona of a Senior Site Reliability Engineer (SRE) / Troubleshooter. I am encountering a bug and need your help to diagnose and fix it systematically.

Error Message / Stack Trace:
{{error_message}}

Expected vs Actual Behavior:
{{behavior_description}}

Relevant Code Context:
{{context_code}}

Please follow this debugging methodology:
1. **Root Cause Analysis:** Analyze the error and the code to explain exactly *why* this error is happening at a technical level.
2. **Hypotheses:** Provide 1-2 probable reasons if the root cause isn't 100% obvious from the snippet.
3. **The Fix:** Provide the exact code changes required to resolve the issue. 
4. **Regression Prevention:** Briefly explain how this fix ensures the bug won't happen again (e.g., edge case handling).

Do not guess blindly. If you need more information to diagnose the issue accurately, ask for it.

Example Usage

Input:

Adopt the persona of a Senior Site Reliability Engineer (SRE) / Troubleshooter. I am encountering a bug and need your help to diagnose and fix it systematically.

Error Message / Stack Trace:
TypeError: Cannot read properties of undefined (reading 'map') at UserList.tsx:24

Expected vs Actual Behavior:
I expected the list of users to render, but instead the app crashes when the API takes too long to respond.

Relevant Code Context:
const UserList = ({ users }) => {
  return <div>{users.map(u => <span key={u.id}>{u.name}</span>)}</div>
}

Please follow this debugging methodology:
[...rest of prompt...]

Read the full file on GitHub · 54 lines

Files

What ships with it

8 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.

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.

  1. 1mo ago First seen · 54 lines · 0 tokens per session scan A 3e08da3bb95d

Subscribe to this mod's changes

debug is a skill published in the GitHub repository DongDuong2001/pudo-code-system (5 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 462 tokens. 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.

Related

Other skills, from other repositories

serena

Serena code intelligence — LSP-powered symbol navigation, diagnostics, and targeted code surgery. Activate before complex refactors, cross-file analysis, or when graph tools need symbol-level depth.

datit309/supergraph · 40 tokens

diagnose

Structured 6-phase debugging. Build feedback loop first, reproduce deterministically, hypothesize with ranked falsifiable theories, instrument one variable at a time, fix with regression test, cleanup. Use when a bug exists, tests fail unexpectedly, or behavior is wrong and cause is unknown.

datit309/supergraph · 59 tokens

fix

Plan-aware auto-fix loop after coding. Runs tests, lint, format, and graph checks. Updates plan task status. Use after execute/tdd.

datit309/supergraph · 33 tokens

zoom-out

One-shot module map — go up a layer of abstraction and get a domain-vocabulary module map of the codebase. Use when lost in unfamiliar code, after a long deep-dive session, or when you need to re-orient before planning.

datit309/supergraph · 53 tokens

diagnose

Diagnostic pipeline for complex/intermittent bugs. Uses diagnostics roles for Investigation, Verification, and Solution before Lead Programmer handoff. Use ONLY for non-obvious failures (root cause unclear, reproduction unstable, fixes reverted). NOT for trivial bugs with known cause — fix them directly.

tranhieutt/software_development_department · 58 tokens

systematic-debugging

Investigates bugs, failing tests, build failures, performance issues, and unexpected behavior with root-cause discipline before any fix is proposed or implemented.

tranhieutt/software_development_department · 34 tokens