Borrowing it
Nothing to install: this file belongs to joshsmithxrm/power-platform-developer-suite. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/joshsmithxrm/power-platform-developer-suite/main/.claude/skills/debug/SKILL.mdgit clone --depth 1 https://github.com/joshsmithxrm/power-platform-developer-suiteWrote 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/joshsmithxrm/power-platform-developer-suite/debug)<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/debug"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/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.
<a href="https://agentmods.dev/skills/joshsmithxrm/power-platform-developer-suite/debug"><img src="https://agentmods.dev/badge/skills/joshsmithxrm/power-platform-developer-suite/debug.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.00028 | $0.02025 |
| Opus 5.5 | $0.00011 | $0.00810 |
| Sonnet 5.5 | $0.00006 | $0.00405 |
| Haiku 4.5 | $0.00003 | $0.00202 |
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.
How it starts
The opening of the file, as written. The whole thing — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug
Systematic debugging for CLI, TUI, Extension, and MCP development. Combines interactive feedback loops with disciplined root-cause analysis.
The Iron Law
NO FIXES WITHOUT ROOT CAUSE INVESTIGATION FIRST.
If you have not completed Phase 1 (Root Cause Investigation), you cannot propose fixes. Period. Skipping this is the single most common source of thrashing, wasted time, and user frustration.
Four Phases (Required Sequence)
Phase 1: Root Cause Investigation
Before touching any code:
- Read error messages carefully — the full message, not just the first line
- Reproduce consistently — if you can't reproduce it, you can't fix it
- Check recent changes —
git diffandgit logfor what changed since it last worked - Gather evidence at component boundaries — logs, network calls, RPC responses, console output
- Trace data flow backward — start from the symptom, trace back through the call chain to find the original trigger
Do NOT skip this phase. Do NOT propose "quick fixes" during this phase.
Phase 2: Pattern Analysis
- Find working examples in the codebase — how do similar features handle this?
- Compare against references — what does the working version do differently?
- Identify differences — the bug is in the delta between working and broken
Phase 3: Hypothesis Testing
- Form a single hypothesis — "The bug is caused by X because of evidence Y"
- Test with the smallest possible change — one variable at a time
- If it doesn't work, form a NEW hypothesis — do NOT stack fixes on top of failed attempts
- Revert failed attempts before trying the next hypothesis
Phase 4: Implementation
- Create a failing test case that reproduces the bug
- Implement a single fix at the root cause (not at the symptom)
- Verify the fix — the test passes, the original error is gone
- If 3+ fixes have failed, STOP — see the escalation rule below
3-Fix Escalation Rule
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.
- 1mo ago First seen · 219 lines · 28 tokens per session scan A ba1d8f71f64c
debug is a skill published in the GitHub repository joshsmithxrm/power-platform-developer-suite (7 stars, last pushed 4d ago), licensed MIT. It adds 28 tokens to every session and 2,025 once invoked, about $0.0001 per session on Opus 5.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
dynamics365-expert
Expert in Dynamics 365 platform, model-driven apps, canvas apps, Power Automate flows, Dataverse, plugins, and custom workflows. Use when the user mentions Microsoft platforms, ERP, CRM, business apps, the Power Platform, or Dataverse, or when the task involves Dynamics 365 Applications, Dataverse Platform…
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.