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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/soleimanmansouri/debug-bank/agents-md"><img src="https://agentmods.dev/badge/instructions/soleimanmansouri/debug-bank/agents-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/agents-md"><img src="https://agentmods.dev/badge/instructions/soleimanmansouri/debug-bank/agents-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.00548 | $0.00548 |
| Opus 5.5 | $0.00219 | $0.00219 |
| Sonnet 5.5 | $0.00110 | $0.00110 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
debug-bank 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 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Bank — Cross-Agent Instructions
This file provides the debug trajectory protocol for any AI coding agent (Codex CLI, Gemini CLI, Cursor, Windsurf, etc.).
Core Protocol
Before Investigating Any Bug
- Read files in
patterns/directory for matching root cause patterns (P01-P21+) - Search
examples/for similar symptoms in domain catalogs - Only then start: Reproduce → Hypothesize → Isolate → Diagnose → Fix → Record
The 7-Step Trajectory
| Step | Action | Output |
|---|---|---|
| 1. Pattern Check | Scan pattern bank for matching root cause | Match or no-match (30 seconds) |
| 2. Reproduce | Get exact error with full output | Logs, stack trace, HTTP status |
| 3. Hypothesize | 2-3 ranked, falsifiable root causes | Ordered list with test for each |
| 4. Isolate | Test hypotheses one at a time | Narrowed to single area |
| 5. Diagnose | Identify single root cause, trace call chain | Root cause statement |
| 6. Fix | Minimal change addressing root cause | Code diff |
| 7. Record | Add trajectory to domain catalog | Structured entry |
Stop Rule
If 3 rounds of iterative fixing show no progress, STOP. Re-plan from scratch or switch strategy.
Recording Format
After fixing, add to the relevant domain catalog:
### [Category] Short Title (YYYY-MM-DD)
- **Symptom:** What was observed
- **Root cause:** The actual technical cause
- **Fix:** What was changed
- **Key insight:** The generalizable lesson
- **Pattern:** P-number if matches existing pattern
Feedback Rules
When corrected by a user, create a persistent rule:
Rule statement.
**Why:** The reason this matters.
**How to apply:** When/where to apply this rule.
Agent-Specific Notes
Codex CLI
- Store patterns in
.codex/patterns/or project rootpatterns/ - Reference this file as
AGENTS.mdin your project root
Gemini CLI
- Store patterns in
.gemini/patterns/or project rootpatterns/ - Gemini CLI reads
AGENTS.mdautomatically
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 · 70 lines · 548 tokens per session scan A 68e22e52c5af
debug-bank AGENTS.md is an instructions file published in the GitHub repository soleimanmansouri/debug-bank (1 stars, last pushed 5mo ago), licensed MIT. It adds 548 tokens to every session, about $0.0022 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.