gsd:phase

gsd:phase is a command for Claude Code from mrboups/xbrain. It costs 22 tokens per session (557 once invoked), scanned A, a copy of gsd:phase, MIT.

A phase manager for maintaining project phases in a ROADMAP.md file, the document that lists planned work.

In plain words
What is it for?
Use it to add a phase, insert a decimal-numbered phase, remove a future phase and renumber later phases, or edit an existing phase.
Why use it?
It keeps the roadmap structured when you need to add, insert, edit, or remove phases, including urgent work between existing phases.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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

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:phase

README.md
[![agentmods](https://agentmods.dev/badge/commands/mrboups/xbrain/phase.svg)](https://agentmods.dev/commands/mrboups/xbrain/phase)
Your own site
<a href="https://agentmods.dev/commands/mrboups/xbrain/phase"><img src="https://agentmods.dev/badge/commands/mrboups/xbrain/phase.svg" alt="Measured on agentmods" height="20"></a>
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 557 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 91% 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.00022 $0.00557
Opus 5 $0.00011 $0.00279
Sonnet 5 $0.00004 $0.00111
Haiku 4.5 $0.00002 $0.00056

Measured 2d ago against content hash 85d7c8e7e834, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade A, and why

gsd: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 2d 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

91% identical to gsd:phase — 8 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/phase.md · 57 lines

What it actually says

Mode routing:

  • default (no flag): Add a new integer phase to the end of the current milestone → add-phase workflow
  • --insert: Insert urgent work as a decimal phase (e.g., 72.1) between existing phases → insert-phase workflow
  • --remove: Remove a future phase and renumber subsequent phases → remove-phase workflow
  • --edit: Edit any field of an existing phase in place → edit-phase workflow
Flag Action Workflow
(none) Add new integer phase at end of milestone add-phase
--insert Insert decimal phase (e.g., 72.1) after specified phase insert-phase
--remove Remove future phase, renumber subsequent remove-phase
--edit Edit fields of existing phase in place edit-phase

<execution_context> @D:/VSC/xbrain/.claude/get-shit-done/workflows/add-phase.md @D:/VSC/xbrain/.claude/get-shit-done/workflows/insert-phase.md @D:/VSC/xbrain/.claude/get-shit-done/workflows/remove-phase.md @D:/VSC/xbrain/.claude/get-shit-done/workflows/edit-phase.md </execution_context>

Parse the first token of $ARGUMENTS:

  • If it is --insert: strip the flag, pass remainder (format: ) to insert-phase workflow
  • If it is --remove: strip the flag, pass remainder (phase number) to remove-phase workflow
  • If it is --edit: strip the flag, pass remainder (phase-number [--force]) to edit-phase workflow
  • Otherwise: pass all of $ARGUMENTS (phase description) to add-phase workflow

Roadmap and state are resolved in-workflow via init phase-op and targeted reads.

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. 2d ago First seen · 57 lines · 22 tokens per session scan A 85d7c8e7e834

Subscribe to this mod's changes

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