debug

debug is an agent for Claude Code from u9401066/template-is-all-you-need. It costs 33 tokens per session (1,658 once invoked), scanned A, original, Apache-2.0.

A debugging agent that investigates software problems using the project's code, history, and decision records. It follows the same Memory Bank process as the coding agent when those project files exist.

In plain words
What is it for?
Use it to analyze bugs, trace likely causes through the codebase, and use past project decisions to guide debugging.
Why use it?
It helps connect a current failure with earlier design decisions and project context, making root-cause investigation more focused.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

Good fit Use it to analyze bugs, trace likely causes through the codebase, and use past project decisions to guide debugging.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/u9401066/template-is-all-you-need/debug
Install

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.

Clone the repo
git clone --depth 1 https://github.com/u9401066/template-is-all-you-need

Made for: Claude Code.

Wrote 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.

agentmods badge for debug

README.md
[![agentmods](https://agentmods.dev/badge/agents/u9401066/template-is-all-you-need/debug/github.svg)](https://agentmods.dev/agents/u9401066/template-is-all-you-need/debug)
Your own site
<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.

agentmods 80×15 button for debug

Your own site · 80×15
<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>
Per session 33 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,658 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash b7be12f7c439, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

.github/agents/debug.agent.md · 161 lines

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

  1. Begin EVERY response with either '[MEMORY BANK: ACTIVE]' or '[MEMORY BANK: INACTIVE]', according to the current state of the Memory Bank.

  2. 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?"
  3. 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.
  4. If Memory Bank Exists:

    • Read ALL memory bank files in this order:
      1. Read productContext.md
      2. Read activeContext.md
      3. Read systemPatterns.md
      4. Read decisionLog.md
      5. Read progress.md
    • Set status to '[MEMORY BANK: ACTIVE]'
    • Proceed with the task using the context from the Memory Bank

Memory Bank Updates

  • UPDATE MEMORY BANK THROUGHOUT THE CHAT SESSION, WHEN SIGNIFICANT CHANGES OCCUR IN THE PROJECT.
  1. 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.
  2. 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.
  3. 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.

Read the full file on GitHub · 161 lines

Changes

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.

  1. 1mo ago First seen · 161 lines · 33 tokens per session scan A b7be12f7c439

Subscribe to this mod's changes

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.