Borrowing it
Nothing to install: this file belongs to svnscha/dap-dbgeng. 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/svnscha/dap-dbgeng/develop/CLAUDE.mdgit clone --depth 1 https://github.com/svnscha/dap-dbgengWrote 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/svnscha/dap-dbgeng/claude-md)<a href="https://agentmods.dev/instructions/svnscha/dap-dbgeng/claude-md"><img src="https://agentmods.dev/badge/instructions/svnscha/dap-dbgeng/claude-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.1 | $0.01534 | $0.01534 |
| Opus 5 | $0.00767 | $0.00767 |
| Sonnet 5 | $0.00307 | $0.00307 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
dap-dbgeng CLAUDE.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 7d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dap-dbgeng
A Windows Debug Adapter Protocol server
backed by the Windows debug engine (dbgeng / dbghelp). DAP-speaking clients (e.g. VS Code)
drive native Windows debugging through it. C++20, CMake + Ninja, vcpkg manifest mode. The single
product is dap-dbgeng.exe, a console app that speaks DAP over stdin/stdout.
Build / test / format
The Ninja build needs the MSVC toolchain on the environment. The npm scripts enter the VS
developer shell automatically (via scripts/With-DevEnv.ps1), so they work from any shell:
npm run configure # cmake --preset windows-x64 (Ninja, vcpkg from VCPKG_ROOT)
npm run build # cmake --build --preset windows-debug
npm test # ctest --preset windows-debug (unit + integration + replay)
npm run generate # regenerate src/protocol from the DAP schema
npm run matrix # regenerate the request coverage page (docs/development/request-coverage.md)
npm run build:vsix # Release adapter + bundle it into the extension + package the VSIX
pwsh scripts/Format.ps1 # clang-format changed files (git-aware)
The extension is TypeScript: npm --prefix vscode run compile type-checks and emits vscode/out
(what main points at, and what vscode:prepublish runs before packaging).
The request coverage matrix is generated, not hand-maintained: npm run matrix rewrites
docs/development/request-coverage.md from the dispatch, handlers, and replay fixtures, and CI runs
npm run matrix:check to fail if the committed page drifts. Regenerate and commit it after adding a
handler or a replay fixture.
Running cmake/ctest directly works too, but only from a VS developer environment (e.g. the
"x64 Native Tools" prompt) so cl/link are on PATH and VCPKG_ROOT points at the bundled vcpkg. Windows-only (dbgeng). vcpkg deps
(vcpkg.json): fmt, nlohmann-json, spdlog, gtest. vcpkg is pinned via builtin-baseline
in vcpkg.json; bump that commit deliberately to move dependency versions (the manifest lists no
per-package version constraints).
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.
- 7d ago First seen · 98 lines · 1,534 tokens per session scan A 1f2ee99f767d
dap-dbgeng CLAUDE.md is an instructions file published in the GitHub repository svnscha/dap-dbgeng (10 stars, last pushed 6d ago), licensed MIT. It adds 1,534 tokens to every session, about $0.0077 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).
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).
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.
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.