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/glslang/windbg-mcp/windbg-debuggingnpx skills add glslang/windbg-mcp --skill windbg-debugginggit clone --depth 1 https://github.com/glslang/windbg-mcpWrote 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/glslang/windbg-mcp/windbg-debugging)<a href="https://agentmods.dev/skills/glslang/windbg-mcp/windbg-debugging"><img src="https://agentmods.dev/badge/skills/glslang/windbg-mcp/windbg-debugging.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 | $0.00071 | $0.03856 |
| Opus 5 | $0.00036 | $0.01928 |
| Sonnet 5 | $0.00014 | $0.00771 |
| Haiku 4.5 | $0.00007 | $0.00386 |
Grade A, and why
windbg-debugging 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 4d 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 — 189 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WinDbg debugging via the windbg MCP server
This skill drives the windbg MCP server, which wraps WinDbg/DbgEng for four kinds of
Windows debugging: crash-dump analysis, live user-mode debugging, kernel
debugging, and Time Travel Debugging (TTD) of .run traces.
Verify the environment first. Most failures are setup, not debugging — wrong engine DLL, missing symbols, or no elevation. Read setup.md before the first session of a workflow you haven't run yet in this environment.
Pick a playbook
| Task | Playbook |
|---|---|
| Build / engine bundling / symbols / elevation / 32-bit .NET | setup.md |
Triage a .dmp crash dump |
crash-dump.md |
| Launch/attach a process, or debug the kernel | live-and-kernel.md |
| Walk kernel pools or user Segment Heaps | heap-walking.md |
Record / open / navigate / analyze a .run trace |
ttd.md |
| Enumerate a driver's IOCTLs & test user-mode reachability | driver-ioctl.md |
Tool map
Knowing which verb exists keeps you from reaching for raw execute when a typed tool
already does the job.
| Group | Tools |
|---|---|
| Session | open_dump, open_trace, attach_kernel_local, attach_kernel, attach_process, launch, end_session, session_status |
| State | registers, read_memory, walk_memory, backtrace (typed frames, each module+RVA as well as its symbol), modules, threads, disassemble, dx |
| Control | go, step_over, step_into, set_breakpoint, run_to_address |
| Transaction | debug_batch — an ordered sequence with assertions and a rollback the engine runs, not the client |
| TTD nav | step_back (t-), step_over_back (p-), reverse_go (g-), goto_position (!tt) |
| TTD analysis | ttd_calls, ttd_memory, ttd_events, index_trace, record_trace |
| Kernel pool | pool_find_tag, pool_chunk, pool_census, pool_diagnostics |
| User Segment Heap | heap_list, heap_allocations, heap_chunk, heap_census, heap_diagnostics |
| Server | server_log — the server's own records: the supervisor's, plus your own sessions' workers, tagged by session |
| Raw | execute — run any debugger command, returns full text output |
What ships with it
6 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.
- 4d ago First seen · 189 lines · 71 tokens per session scan A af23af997ecc
windbg-debugging is a skill published in the GitHub repository glslang/windbg-mcp (9 stars, last pushed today), licensed MIT. It adds 71 tokens to every session and 3,856 once invoked, about $0.0004 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
debugger-driven-analysis
Drive runtime analysis with debugger-first workflows for breakpoint planning, register and memory observation, and static-to-dynamic correlation. Use when static analysis is insufficient or runtime behavior must be confirmed.
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.