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 instructions/kanren3/windbg-mcp/agents-mdgit clone --depth 1 https://github.com/kanren3/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/instructions/kanren3/windbg-mcp/agents-md)<a href="https://agentmods.dev/instructions/kanren3/windbg-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kanren3/windbg-mcp/agents-md.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.02033 | $0.02033 |
| Opus 5 | $0.01017 | $0.01017 |
| Sonnet 5 | $0.00407 | $0.00407 |
| Haiku 4.5 | $0.00203 | $0.00203 |
Grade A, and why
windbg-mcp AGENTS.md 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 5d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Overview
windbg-mcp is a Windows-only, zero-dependency TypeScript MCP server running on Bun. It drives cdb.exe (user mode) and kd.exe (kernel mode) as Win32 subprocesses and exposes WinDbg debugging — crash-dump analysis, live process debugging, kernel debugging — to LLM agents over the Model Context Protocol.
The MCP protocol is hand-rolled (no @modelcontextprotocol/sdk): newline-delimited JSON-RPC 2.0 over stdio. It supports both the server/discover era (2026-07-28) and legacy initialize version negotiation.
Architecture & Data Flow
stdin (JSON-RPC lines)
→ src/index.ts serialized dispatch (promise-chain `tail`)
→ src/mcp.ts McpServer.handle → tool methods
→ src/session.ts DebuggerSession + factories
→ src/spawn_win32.ts kernel32.dll FFI (CreateProcessW)
→ cdb.exe / kd.exe child process, piped stdio
→ marker protocol `.echo COMMAND_COMPLETED_MARKER_N`
→ stdout (JSON-RPC response lines)
src/index.ts— entry point (#!/usr/bin/env bun). Buffers stdin, splits newline-delimited JSON, and chains each dispatch ontotailso pipelined requests cannot interleave and corrupt the marker protocol. Handles parse errors (-32700). Cleans up child processes on SIGINT/SIGTERM/SIGHUP (async) andexit(sync).src/mcp.ts—McpServerclass, the session registry (Map<string, SessionRecord>), and all 10windbg_*tool definitions and implementations. Also serves the guide andwindbg://command/{id}resources.src/session.ts—DebuggerSession: one cdb/kd child per session. Owns the marker protocol, prompt detection, execution-state inference, and child lifecycle (start/execute/interrupt/close/detach/killSync). Exposes factory functionscreateCdbExecutableSession,createCdbDumpSession,createCdbAttachSession,createKdSession.src/spawn_win32.ts— rawkernel32.dllFFI viabun:ffi(dlopen), with manualSTARTUPINFOW/PROCESS_INFORMATIONstruct layouts. Spawns withCREATE_NEW_PROCESS_GROUPand piped stdio.src/catalog.ts—Catalogsingleton loadingsrc/data/catalog.json; search scoring andwindbg://command/...URI resolution.src/resources.ts— text renderers for the guide and command cards.
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.
- 5d ago First seen · 103 lines · 2,033 tokens per session scan A d3612b50167b
windbg-mcp AGENTS.md is an instructions file published in the GitHub repository kanren3/windbg-mcp (5 stars, last pushed 21d ago), licensed MIT. It adds 2,033 tokens to every session, about $0.0102 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).