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/votruongdanh/skills-agent/debugnpx skills add VoTruongDanh/Skills-Agent --skill debuggit clone --depth 1 https://github.com/VoTruongDanh/Skills-AgentWrote 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/votruongdanh/skills-agent/debug)<a href="https://agentmods.dev/skills/votruongdanh/skills-agent/debug"><img src="https://agentmods.dev/badge/skills/votruongdanh/skills-agent/debug.svg" alt="Measured on agentmods" 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.00055 | $0.00969 |
| Opus 5 | $0.00028 | $0.00485 |
| Sonnet 5 | $0.00011 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
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 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Memory Protocol
START: Read .ai-memory.md from project root. Check for known bugs, past fixes, tech stack details, common error patterns, and architecture notes.
END: Update .ai-memory.md using Memory Compaction Rules with: bug, root cause, fix, files touched, lessons learned, and remaining risks.
Goal
Find the real root cause, not just the first visible symptom.
Agent Routing
- If bug is in API/server/backend → read
.kiro/skills/agents/agents/backend-specialist.mdand apply its knowledge - If bug is in UI/rendering/CSS → read
.kiro/skills/agents/agents/frontend-specialist.mdand apply its knowledge - If bug is in database/queries → read
.kiro/skills/agents/agents/database-architect.mdand apply its knowledge - If bug may be a security issue → read
.kiro/skills/agents/agents/security-auditor.mdand apply its knowledge - Default → read
.kiro/skills/agents/agents/debugger.mdand apply its systematic analysis
Socratic Gate
Before debugging, verify:
- What is the expected behavior vs actual behavior?
- Is there a log, stacktrace, or error message?
- When did this start? (recent change, always broken, intermittent?)
- Have we tried this before? If any answer is missing, ASK before proceeding.
Workflow
- Read Memory — Load
.ai-memory.mdfor project context and past bug history. - Summarize the bug, expected behavior, and actual behavior.
- Gather evidence from logs, stack traces, code paths, config, and recent changes.
- List the top hypotheses ranked by likelihood. Eliminate previously failed hypotheses immediately.
- Eliminate hypotheses using direct evidence.
- Identify the root cause and confirm with evidence before attempting any code changes.
- Propose an effective solution that addresses the root cause definitively. Ensure clean code standards are met and fully update all related files.
- Suggest how to verify the fix and prevent regressions.
- Quality Gate — Read
.kiro/skills/_scripts/checklist.mdand run cross-cutting quality checks. - Update Memory — Save root cause, fix, and lessons to
.ai-memory.md.
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 · +3 lines fbe529a8d2a8
- 5d ago First seen · 79 lines · 55 tokens per session scan A 25b11f7497ec
debug is a skill published in the GitHub repository VoTruongDanh/Skills-Agent (2 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 969 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
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.
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
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…