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

.claude/commands/gsd/new-project.md

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

A command for starting a new software project by gathering context, optionally researching the subject area, defining requirements, and creating a roadmap. It also records project decisions and workflow settings in planning files.

In plain words
What is it for?
Use it to create project documentation, requirements, a phased roadmap, and saved project context ready for planning the first phase.
Why use it?
It turns an early idea into an agreed scope and sequence of work before implementation begins.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: 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 →

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

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/new-project.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:new-project

README.md
[![agentmods](https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/new-project.svg)](https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/new-project)
Your own site
<a href="https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/new-project"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/new-project.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 6,671 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 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.1 $0.00016 $0.06671
Opus 5 $0.00008 $0.03335
Sonnet 5 $0.00003 $0.01334
Haiku 4.5 $0.00002 $0.00667

Measured 7d ago against content hash b178940bd251, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

gsd:new-project 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 7d 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

100% identical to gsd:new-project — 0 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/new-project.md · 1,009 lines

How it starts

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

Initialize a new project through unified flow: questioning → research (optional) → requirements → roadmap.

This is the most leveraged moment in any project. Deep questioning here means better plans, better execution, better outcomes. One command takes you from idea to ready-for-planning.

Creates:

  • .planning/PROJECT.md — project context
  • .planning/config.json — workflow preferences
  • .planning/research/ — domain research (optional)
  • .planning/REQUIREMENTS.md — scoped requirements
  • .planning/ROADMAP.md — phase structure
  • .planning/STATE.md — project memory

After this command: Run /gsd:plan-phase 1 to start execution.

<execution_context>

@./.claude/get-shit-done/references/questioning.md @./.claude/get-shit-done/references/ui-brand.md @./.claude/get-shit-done/templates/project.md @./.claude/get-shit-done/templates/requirements.md

</execution_context>

Phase 1: Setup

MANDATORY FIRST STEP — Execute these checks before ANY user interaction:

  1. Abort if project exists:

    [ -f .planning/PROJECT.md ] && echo "ERROR: Project already initialized. Use /gsd:progress" && exit 1
    
  2. Initialize git repo in THIS directory (required even if inside a parent repo):

    if [ -d .git ] || [ -f .git ]; then
        echo "Git repo exists in current directory"
    else
        git init
        echo "Initialized new git repo"
    fi
    
  3. Detect existing code (brownfield detection):

    CODE_FILES=$(find . -name "*.ts" -o -name "*.js" -o -name "*.py" -o -name "*.go" -o -name "*.rs" -o -name "*.swift" -o -name "*.java" 2>/dev/null | grep -v node_modules | grep -v .git | head -20)
    HAS_PACKAGE=$([ -f package.json ] || [ -f requirements.txt ] || [ -f Cargo.toml ] || [ -f go.mod ] || [ -f Package.swift ] && echo "yes")
    HAS_CODEBASE_MAP=$([ -d .planning/codebase ] && echo "yes")
    

    You MUST run all bash commands above using the Bash tool before proceeding.

Read the full file on GitHub · 1,009 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. 7d ago First seen · 1,009 lines · 16 tokens per session scan A b178940bd251

Subscribe to this mod's changes

gsd:new-project is a command published in the GitHub repository Jamie-BitFlight/git-project-xray-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 16 tokens to every session and 6,671 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:new-project, differing in 0 lines, and is treated as a copy.