gsd:debug

A structured debugging workflow that investigates software problems and keeps its progress between sessions.

In plain words
What is it for?
Use it to diagnose bugs, review active investigations, check a session's status, or continue a paused debugging session.
Why use it?
It helps narrow down the real cause of a bug when several failure paths are possible, instead of guessing at fixes.

Command for Claude Code

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/mrboups/xbrain/debug
Clone the repo
git clone --depth 1 https://github.com/mrboups/xbrain

Made for: Claude Code.

Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,273 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod 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.00014 $0.02273
Opus 5 $0.00007 $0.01137
Sonnet 5 $0.00003 $0.00455
Haiku 4.5 $0.00001 $0.00227

Measured yesterday against content hash ab3328459775, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

gsd: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.

Origin

This is a copy

100% identical to gsd:debug — 6 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/gsd/debug.md · 264 lines

How it starts

The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Orchestrator role: Gather symptoms, spawn gsd-debugger agent, handle checkpoints, spawn continuations.

Why subagent: Investigation burns context fast (reading files, forming hypotheses, testing). Fresh 200k context per investigation. Main context stays lean for user interaction.

Flags:

  • --diagnose — Diagnose only. Find root cause without applying a fix. Returns a structured Root Cause Report. Use when you want to validate the diagnosis before committing to a fix.

Subcommands:

  • list — List all active debug sessions
  • status <slug> — Print full summary of a session without spawning an agent
  • continue <slug> — Resume a specific session by slug

<available_agent_types> Valid GSD subagent types (use exact names — do not fall back to 'general-purpose'):

  • gsd-debug-session-manager — manages debug checkpoint/continuation loop in isolated context
  • gsd-debugger — investigates bugs using scientific method </available_agent_types>

Parse subcommands and flags from $ARGUMENTS BEFORE the active-session check:

  • If $ARGUMENTS starts with "list": SUBCMD=list, no further args
  • If $ARGUMENTS starts with "status ": SUBCMD=status, SLUG=remainder (trim whitespace)
  • If $ARGUMENTS starts with "continue ": SUBCMD=continue, SLUG=remainder (trim whitespace)
  • If $ARGUMENTS contains --diagnose: SUBCMD=debug, diagnose_only=true, strip --diagnose from description
  • Otherwise: SUBCMD=debug, diagnose_only=false

Check for active sessions (used for non-list/status/continue flows):

ls .planning/debug/*.md 2>/dev/null | grep -v resolved | head -5

0. Initialize Context

INIT=$(gsd-sdk query state.load)
if [[ "$INIT" == @file:* ]]; then INIT=$(cat "${INIT#@file:}"); fi

Extract commit_docs from init JSON. Resolve debugger model:

debugger_model=$(gsd-sdk query resolve-model gsd-debugger 2>/dev/null | jq -r '.model' 2>/dev/null || true)

Read TDD mode from config:

TDD_MODE=$(gsd-sdk query config-get workflow.tdd_mode 2>/dev/null | jq -r 'if type == "boolean" then tostring else . end' 2>/dev/null || echo "false")

Read the full file on GitHub · 264 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. yesterday First seen · 264 lines · 0 tokens per session scan A ab3328459775

Subscribe to this mod's changes

gsd:debug is a command published in the GitHub repository mrboups/xbrain (2 stars, last pushed 17d ago), licensed MIT. It adds 14 tokens to every session and 2,273 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gsd:debug, differing in 6 lines, and is treated as a copy.