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

.claude/commands/gsd/research-phase.md

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

A command for researching how to implement one development phase before deciding or writing a plan. A phase is one numbered piece of a larger project roadmap.

In plain words
What is it for?
Use it to research a roadmap phase, check existing research, gather sources and context, and present the findings.
Why use it?
It lets you investigate feasibility and gather context separately, including when a phase needs to be researched again after planning.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions subagents.

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 →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is prompt="First, read ./.claude/agents/gsd-phase-researcher.md for your role and instructions.\n\n" + filled_prompt,.

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/research-phase.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:research-phase

README.md
[![agentmods](https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/research-phase.svg)](https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/research-phase)
Your own site
<a href="https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/research-phase"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/research-phase.svg" alt="Measured on agentmods" height="20"></a>
Per session 26 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,472 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 86% 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.00026 $0.01472
Opus 5 $0.00013 $0.00736
Sonnet 5 $0.00005 $0.00294
Haiku 4.5 $0.00003 $0.00147

Measured 6d ago against content hash 0f6ac5424018, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

gsd:research-phase 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 6d 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

86% identical to gsd:research-phase — 83 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/research-phase.md · 201 lines

How it starts

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

Note: This is a standalone research command. For most workflows, use /gsd:plan-phase which integrates research automatically.

Use this command when:

  • You want to research without planning yet
  • You want to re-research after planning is complete
  • You need to investigate before deciding if a phase is feasible

Orchestrator role: Parse phase, validate against roadmap, check existing research, gather context, spawn researcher agent, present results.

Why subagent: Research burns context fast (WebSearch, Context7 queries, source verification). Fresh 200k context for investigation. Main context stays lean for user interaction.

Normalize phase input in step 1 before any directory lookups.

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-phase-researcher opus sonnet haiku

Store resolved model for use in Task calls below.

1. Normalize and Validate Phase

# Normalize phase number (8 → 08, but preserve decimals like 2.1 → 02.1)
if [[ "$ARGUMENTS" =~ ^[0-9]+$ ]]; then
  PHASE=$(printf "%02d" "$ARGUMENTS")
elif [[ "$ARGUMENTS" =~ ^([0-9]+)\.([0-9]+)$ ]]; then
  PHASE=$(printf "%02d.%s" "${BASH_REMATCH[1]}" "${BASH_REMATCH[2]}")
else
  PHASE="$ARGUMENTS"
fi

grep -A5 "Phase ${PHASE}:" .planning/ROADMAP.md 2>/dev/null

If not found: Error and exit. If found: Extract phase number, name, description.

2. Check Existing Research

ls .planning/phases/${PHASE}-*/RESEARCH.md 2>/dev/null

If exists: Offer: 1) Update research, 2) View existing, 3) Skip. Wait for response.

Read the full file on GitHub · 201 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. 6d ago First seen · 201 lines · 26 tokens per session scan A 0f6ac5424018

Subscribe to this mod's changes

gsd:research-phase is a command published in the GitHub repository Jamie-BitFlight/git-project-xray-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 26 tokens to every session and 1,472 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to gsd:research-phase, differing in 83 lines, and is treated as a copy.