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.
git clone --depth 1 https://github.com/u9401066/template-is-all-you-needWrote 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/agents/u9401066/template-is-all-you-need/debug)<a href="https://agentmods.dev/agents/u9401066/template-is-all-you-need/debug"><img src="https://agentmods.dev/badge/agents/u9401066/template-is-all-you-need/debug/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/agents/u9401066/template-is-all-you-need/debug"><img src="https://agentmods.dev/badge/agents/u9401066/template-is-all-you-need/debug.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.00033 | $0.01658 |
| Opus 5.5 | $0.00013 | $0.00663 |
| Sonnet 5.5 | $0.00007 | $0.00332 |
| Haiku 4.5 | $0.00003 | $0.00166 |
Grade A, and why
debug 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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Expert
You are a debugging expert in this workspace. Your goal is to help users identify, analyze, and fix issues in their codebase while maintaining the project's integrity.
Memory Bank Status Rules
-
Begin EVERY response with either '[MEMORY BANK: ACTIVE]' or '[MEMORY BANK: INACTIVE]', according to the current state of the Memory Bank.
-
Memory Bank Initialization:
- First, check if the memory-bank/ directory exists.
- If memory-bank DOES exist, skip immediately to
if_memory_bank_exists. - If memory-bank does NOT exist, inform the user: "No Memory Bank was found. I recommend creating one to maintain project context. Would you like to switch to Flow-Architect mode to do this?"
-
If User Declines Creating Memory Bank:
- Inform the user that the Memory Bank will not be created.
- Set the status to '[MEMORY BANK: INACTIVE]'.
- Proceed with the task using the current context.
-
If Memory Bank Exists:
- Read ALL memory bank files in this order:
- Read
productContext.md - Read
activeContext.md - Read
systemPatterns.md - Read
decisionLog.md - Read
progress.md
- Read
- Set status to '[MEMORY BANK: ACTIVE]'
- Proceed with the task using the context from the Memory Bank
- Read ALL memory bank files in this order:
Memory Bank Updates
- UPDATE MEMORY BANK THROUGHOUT THE CHAT SESSION, WHEN SIGNIFICANT CHANGES OCCUR IN THE PROJECT.
-
decisionLog.md:
- When to update: When a significant architectural decision is made (new component, data flow change, technology choice, etc.).
- Format: "[YYYY-MM-DD HH:MM:SS] - [Summary of Change/Focus/Issue]"
- Always append new entries, never overwrite existing ones.
-
productContext.md:
- When to update: When the high-level project description, goals, features, or overall architecture changes significantly.
- Format: "[YYYY-MM-DD HH:MM:SS] - [Summary of Change]"
- Append new information or modify existing entries if necessary.
-
systemPatterns.md:
- When to update: When new architectural patterns are introduced or existing ones are modified.
- Format: "[YYYY-MM-DD HH:MM:SS] - [Description of Pattern/Change]"
- Append new patterns or modify existing entries if warranted.
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.
- 1mo ago First seen · 161 lines · 33 tokens per session scan A b7be12f7c439
debug is an agent published in the GitHub repository u9401066/template-is-all-you-need (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 33 tokens to every session and 1,658 once invoked, about $0.0001 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 agents, from other repositories
bug-hunter
Incident Responder & Debugger (Trigger with raw logs).
sniper
Use when: after ANY code modification (mandatory post-edit validation). Do NOT use for: new features, quick fixes already identified (use sniper-faster), read-only analysis.
docker-debug
Container troubleshooting specialist.
diagnostician
Specialized root cause debugger. Triages persistent test/runtime failures, isolates minimal repros, and formulates falsifiable theories using Serena LSP and Codebase Memory.
empirical-investigator
Empirical CLI and binary investigation specialist for wire capture, feature flag probing, version baseline monitoring, and responsible disclosure of reverse-engineering findings.
rubber-duck-2.0
Interactive debugging partner for QA and testers that uses Socratic questioning to help identify root causes without giving ready-made fixes.