git-project-xray-mcp: Command for Claude Code

.claude/commands/gsd/debug.md

gsd:debug is a command for Claude Code from Jamie-BitFlight/git-project-xray-mcp. It costs 14 tokens per session (961 once invoked), scanned A, a copy of gsd-debug, MIT.

A command for investigating software problems through a structured process while saving progress between sessions. It gathers symptoms, tests possible causes, and tracks unfinished investigations.

In plain words
What is it for?
Use it to investigate bugs, record hypotheses and next steps, and resume an active debugging session.
Why use it?
It prevents debugging work from being lost when the agent reaches a context limit or needs to continue later.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents; names the AskUserQuestion tool.

This is Jamie-BitFlight/git-project-xray-mcp's own configuration. It tells Claude Code how to work on git-project-xray-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything git-project-xray-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to Jamie-BitFlight/git-project-xray-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Jamie-BitFlight/git-project-xray-mcp/main/.claude/commands/gsd/debug.md
Clone the repo
git clone --depth 1 https://github.com/Jamie-BitFlight/git-project-xray-mcp

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/debug/github.svg)](https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/debug)
Your own site
<a href="https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/debug"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/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 gsd:debug

Your own site · 80×15
<a href="https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/debug"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/debug.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 961 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 89% 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.1 $0.00014 $0.00961
Opus 5.5 $0.00006 $0.00384
Sonnet 5.5 $0.00003 $0.00192
Haiku 4.5 $0.00001 $0.00096

Measured 1mo ago against content hash f519b4889173, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

89% identical to gsd-debug — 42 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 · 170 lines

How it starts

The opening of the file, as written. The whole thing — 170 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.

Check for active sessions:

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

0. Resolve Model Profile

Read model profile for agent spawning:

MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")

Default to "balanced" if not set.

Model lookup table:

Agent quality balanced budget
gsd-debugger opus sonnet sonnet

Store resolved model for use in Task calls below.

1. Check Active Sessions

If active sessions exist AND no $ARGUMENTS:

  • List sessions with status, hypothesis, next action
  • User picks number to resume OR describes new issue

If $ARGUMENTS provided OR user describes new issue:

  • Continue to symptom gathering

2. Gather Symptoms (if new issue)

Use AskUserQuestion for each:

  1. Expected behavior - What should happen?
  2. Actual behavior - What happens instead?
  3. Error messages - Any errors? (paste or describe)
  4. Timeline - When did this start? Ever worked?
  5. Reproduction - How do you trigger it?

After all gathered, confirm ready to investigate.

3. Spawn gsd-debugger Agent

Fill prompt and spawn:

<objective>
Investigate issue: {slug}

**Summary:** {trigger}
</objective>

<symptoms>
expected: {expected}
actual: {actual}
errors: {errors}
reproduction: {reproduction}
timeline: {timeline}
</symptoms>

<mode>
symptoms_prefilled: true
goal: find_and_fix
</mode>

<debug_file>
Create: .planning/debug/{slug}.md
</debug_file>

Read the full file on GitHub · 170 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 · 170 lines · 14 tokens per session scan A f519b4889173

Subscribe to this mod's changes

gsd:debug is a command published in the GitHub repository Jamie-BitFlight/git-project-xray-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 14 tokens to every session and 961 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to gsd-debug, differing in 42 lines, and is treated as a copy.