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.
npx agentmods add commands/jamie-bitflight/git-project-xray-mcp/helpgit clone --depth 1 https://github.com/Jamie-BitFlight/git-project-xray-mcpWrote 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.
[](https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/help)<a href="https://agentmods.dev/commands/jamie-bitflight/git-project-xray-mcp/help"><img src="https://agentmods.dev/badge/commands/jamie-bitflight/git-project-xray-mcp/help.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00013 | $0.03465 |
| Opus 5 | $0.00006 | $0.01733 |
| Sonnet 5 | $0.00003 | $0.00693 |
| Haiku 4.5 | $0.00001 | $0.00347 |
Grade A, and why
gsd:help 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 3d 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.
This is a copy
100% identical to gsd:help — 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.
How it starts
The opening of the file, as written. The whole thing — 483 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Output ONLY the reference content below. Do NOT add:
- Project-specific analysis
- Git status or file context
- Next-step suggestions
- Any commentary beyond the reference
GSD (Get Shit Done) creates hierarchical project plans optimized for solo agentic development with Claude Code.
Quick Start
/gsd:new-project- Initialize project (includes research, requirements, roadmap)/gsd:plan-phase 1- Create detailed plan for first phase/gsd:execute-phase 1- Execute the phase
Staying Updated
GSD evolves fast. Update periodically:
npx get-shit-done-cc@latest
Core Workflow
/gsd:new-project → /gsd:plan-phase → /gsd:execute-phase → repeat
Project Initialization
/gsd:new-project
Initialize new project through unified flow.
One command takes you from idea to ready-for-planning:
- Deep questioning to understand what you're building
- Optional domain research (spawns 4 parallel researcher agents)
- Requirements definition with v1/v2/out-of-scope scoping
- Roadmap creation with phase breakdown and success criteria
Creates all .planning/ artifacts:
PROJECT.md— vision and requirementsconfig.json— workflow mode (interactive/yolo)research/— domain research (if selected)REQUIREMENTS.md— scoped requirements with REQ-IDsROADMAP.md— phases mapped to requirementsSTATE.md— project memory
Usage: /gsd:new-project
/gsd:map-codebase
Map an existing codebase for brownfield projects.
- Analyzes codebase with parallel Explore agents
- Creates
.planning/codebase/with 7 focused documents - Covers stack, architecture, structure, conventions, testing, integrations, concerns
- Use before
/gsd:new-projecton existing codebases
Usage: /gsd:map-codebase
Phase Planning
/gsd:discuss-phase <number>
Help articulate your vision for a phase before planning.
- Captures how you imagine this phase working
- Creates CONTEXT.md with your vision, essentials, and boundaries
- Use when you have ideas about how something should look/feel
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.
- 3d ago First seen · 483 lines · 13 tokens per session scan A e81e596f5332
gsd:help is a command published in the GitHub repository Jamie-BitFlight/git-project-xray-mcp (0 stars, last pushed 6mo ago), licensed MIT. It adds 13 tokens to every session and 3,465 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:help, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.