agentmods.dev

debug

A structured debugging procedure for investigating software errors from their evidence to their underlying cause.

In plain words
What is it for?
Use it to inspect stack traces or logs, locate the failing code, test at least two possible causes, fix the root problem, and run tests.
Why use it?
It replaces guesswork with reproducible checks, competing explanations, a verified fix, and a record of the result.

Command for Claude Code

8 2mo ago A scan 0 tokens original MIT
View the source file luiseiman/dotforge
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.

agentmods
npx agentmods add commands/luiseiman/dotforge/debug
Clone the repo
git clone --depth 1 https://github.com/luiseiman/dotforge

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 300 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00300
Opus 5 $0.00000 $0.00150
Sonnet 5 $0.00000 $0.00060
Haiku 4.5 $0.00000 $0.00030

Measured yesterday against content hash ee8fcab326af, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 yesterday.

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.

.claude/commands/debug.md · 37 lines

What it actually says

Debug

Diagnóstico estructurado de un error.

Argumentos

$ARGUMENTS: descripción del error, stack trace, o "último error" para buscar en logs.

Proceso

  1. Recopilar evidencia:

    • Si hay stack trace en $ARGUMENTS, parsearlo
    • Si no, buscar en logs recientes o preguntar al usuario
    • Leer el código del archivo/línea del error

  2. Análisis paso a paso:

    • ¿Qué línea exacta falla?
    • ¿Qué valor tiene cada variable relevante?
    • ¿Qué condición no se cumple?
    • ¿Es reproducible? ¿Cuándo ocurre?

  3. Hipótesis (mínimo 2):

    • Hipótesis A: causa más probable + evidencia
    • Hipótesis B: causa alternativa + evidencia

  4. Verificación:

    • Ejecutar test que reproduce el error (o crear uno)
    • Confirmar cuál hipótesis es correcta

  5. Fix:

    • Corregir la causa raíz (no el síntoma)
    • Ejecutar tests para verificar que el fix funciona
    • Verificar que no se rompió nada más

  6. Registro:

    • Si existe CLAUDE_ERRORS.md, registrar el error con causa raíz y fix
    • Formato: | fecha | área | error | causa | fix | regla |
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. yesterday First seen · 37 lines · 0 tokens per session scan A ee8fcab326af

Subscribe to this mod's changes

debug is a command published in the GitHub repository luiseiman/dotforge (8 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 300 tokens. 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.

Data and AIDebuggingTestingai-codinganthropicclaude-codeclaude-code-agentsclaude-code-auditclaude-code-config
Related

Other commands, from other repositories

get-to-work

Autonomous ops work. Args: [mode] [repeat]. Modes: tasks | opps | full | escalating (default). Repeat: cycle (keep going, default) | once (single pass). Run this before stepping away from an ops repo.

OdinMB/ops-workflow · 66 tokens

recap

Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…

OdinMB/ops-workflow · 105 tokens

whats-next

Generate an executive overview of the project. Synthesizes state, backlogs, and recent plans into a ranked action plan answering "What should we do next?".

OdinMB/ops-workflow · 32 tokens

batch-execute

Execute a batch of ops plans continuously without user input, storing any issues and user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.

OdinMB/ops-workflow · 44 tokens

batch-plan

Create a batch of ops plans continuously without user input, storing any user questions in a .md file to be processed with the user afterwards. Do NOT invoke this yourself! Should only be invoked by the user.

OdinMB/ops-workflow · 42 tokens

find-all

Run both ops finders in parallel (tasks, opps) and brief you on what they found. Discovery only — no plans, no execution.

OdinMB/ops-workflow · 30 tokens