Borrowing it
Nothing to install: this file belongs to soleimanmansouri/debug-bank. 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/soleimanmansouri/debug-bank/main/CLAUDE.mdgit clone --depth 1 https://github.com/soleimanmansouri/debug-bankWrote 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/soleimanmansouri/debug-bank/claude-md)<a href="https://agentmods.dev/instructions/soleimanmansouri/debug-bank/claude-md"><img src="https://agentmods.dev/badge/instructions/soleimanmansouri/debug-bank/claude-md/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/instructions/soleimanmansouri/debug-bank/claude-md"><img src="https://agentmods.dev/badge/instructions/soleimanmansouri/debug-bank/claude-md.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.00799 | $0.00799 |
| Opus 5.5 | $0.00320 | $0.00320 |
| Sonnet 5.5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
debug-bank 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 2mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Bank — Debug Trajectory Protocol
Debugging Protocol
Follow this exact chain for every debugging session. Each step produces evidence for the next — never skip.
Before Investigating
- Pattern Check — Read
patterns/for matching root cause type. If a match exists, verify the known fix applies before re-investigating. This takes 30 seconds and saves hours. - Domain Search — Search your domain catalogs (if any) for similar symptoms.
The Trajectory
- Reproduce — Get the exact error. Capture full output (logs, stack trace, HTTP status). If you can't reproduce, add logging and try again.
- Hypothesize — State 2-3 possible root causes ranked by likelihood. Each hypothesis must be falsifiable with a specific test.
- Isolate — Test hypotheses one at a time. Use binary search: disable half the system, check if bug persists, narrow.
- Diagnose — Identify the single root cause. Trace the full call chain from trigger to symptom. Check for "root cause behind the root cause."
- Fix — Minimal change. Verify the fix addresses the root cause, not a symptom.
- Record — Add the trajectory to your domain catalog using this format:
### [Category] Short Title (date) - **Symptom:** What the user/system saw - **Root cause:** The actual technical cause - **Fix:** What was changed (file:line) - **Key insight:** The generalizable lesson - **Pattern:** P-number if it matches an existing pattern
The 3-Exchange Rule
If 3 rounds of iterative fixing show no progress: STOP. Do not continue the same approach.
Instead:
- Re-plan from scratch with everything you now know
- Add logging/instrumentation to gather new evidence
- Switch strategy entirely (e.g., from code-level fix to config-level fix)
Anti-Patterns (Enforced)
- Never fix a symptom without finding the root cause
- Never apply a fix you saw work elsewhere without verifying it matches the current root cause
- Never keep iterating past 3 exchanges — switch strategy
- Never assume you understand the bug from the description alone — always reproduce first
- Always check if 2+ symptoms share one root cause before filing separate fixes
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.
- 2mo ago First seen · 77 lines · 799 tokens per session scan A 7e3528c944dc
debug-bank CLAUDE.md is an instructions file published in the GitHub repository soleimanmansouri/debug-bank (1 stars, last pushed 5mo ago), licensed MIT. It adds 799 tokens to every session, about $0.0032 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 instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.