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 d-gangz/dgang-skills --skill debug-agentgit clone --depth 1 https://github.com/d-gangz/dgang-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/d-gangz/dgang-skills/debug-agent)<a href="https://agentmods.dev/skills/d-gangz/dgang-skills/debug-agent"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/debug-agent/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/d-gangz/dgang-skills/debug-agent"><img src="https://agentmods.dev/badge/skills/d-gangz/dgang-skills/debug-agent.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00142 | $0.02733 |
| Opus 5 | $0.00071 | $0.01367 |
| Sonnet 5 | $0.00028 | $0.00547 |
| Haiku 4.5 | $0.00014 | $0.00273 |
Grade A, and why
debug-agent 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 10d 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Agent
Diagnose what went wrong in this session and apply the right fixes. Two invocation modes:
- Failure-driven (typical) — user saw a specific bad output ("the dossier missed the qualification criteria"). Anchor on that symptom.
- Generic review — user wants a retrospective ("how did this session go", "anything we could've done better"). No named failure; scan for the most prominent issues.
Two roles
This skill runs in one of two roles. Identify which one you are before doing anything else, then follow only that section.
- §MAIN — you received
/debug-agent(or an equivalent ask) from the user directly. You own user interaction and you apply any fixes. You do not diagnose inline — you spawn a fork to do that. - §FORK — you were spawned by a
/debug-agentMAIN with a directive containing the phrase "diagnose only — return report, do not edit". You own the diagnosis and return a structured report. You never edit files.
If the directive that brought you here doesn't contain that phrase, you are MAIN.
Hard constraint (both roles)
Only diagnose the current session. Do not read other transcripts, session logs, or external traces. Evidence comes from this conversation's own history. (Forks inherit the conversation, so they have it natively.)
§MAIN — Workflow
You are the user-facing agent. Your job is small: dispatch the fork, present what it returns, and apply the fix only after explicit approval.
1. Fork yourself for diagnosis
Immediately spawn a fork via the Agent tool with no subagent_type (a fork inherits this conversation's context, which is the entire evidence base). Name it something like debug-diagnosis.
The fork's directive must:
- Tell it to invoke this skill (
/debug-agent) so it loads the §FORK instructions. - Contain the literal phrase "diagnose only — return report, do not edit" so it routes to §FORK.
- Tell it to return a structured report (shape described in §FORK step 6).
What ships with it
5 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.
- 10d ago First seen · 210 lines · 142 tokens per session scan A 05779a1d628c
debug-agent is a skill published in the GitHub repository d-gangz/dgang-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 142 tokens to every session and 2,733 once invoked, about $0.0007 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.