gsd:plan-milestone-gaps

gsd:plan-milestone-gaps is a command for Claude Code from YousefNabil-SOC/claude-apex. It costs 20 tokens per session (261 once invoked), scanned A, a copy of gsd:plan-milestone-gaps, MIT.

A planning command that turns problems found in a milestone review into work phases. A milestone is a major project checkpoint, and a roadmap is the project's list of planned work.

In plain words
What is it for?
Use it after a milestone audit to read MILESTONE-AUDIT.md, group related gaps, add phases to ROADMAP.md, and optionally plan them.
Why use it?
It removes the need to create a separate phase manually for every identified gap.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; names the AskUserQuestion tool.

Good fit Use it after a milestone audit to read MILESTONE-AUDIT.md, group related gaps, add phases to ROADMAP.md, and optionally plan them.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yousefnabil-soc/claude-apex/plan-milestone-gaps
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.

Clone the repo
git clone --depth 1 https://github.com/YousefNabil-SOC/claude-apex

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:plan-milestone-gaps

README.md
[![agentmods](https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/plan-milestone-gaps/github.svg)](https://agentmods.dev/commands/yousefnabil-soc/claude-apex/plan-milestone-gaps)
Your own site
<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/plan-milestone-gaps"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/plan-milestone-gaps/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:plan-milestone-gaps

Your own site · 80×15
<a href="https://agentmods.dev/commands/yousefnabil-soc/claude-apex/plan-milestone-gaps"><img src="https://agentmods.dev/badge/commands/yousefnabil-soc/claude-apex/plan-milestone-gaps.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 261 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.00020 $0.00261
Opus 5 $0.00010 $0.00130
Sonnet 5 $0.00004 $0.00052
Haiku 4.5 $0.00002 $0.00026

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

Security

Grade A, and why

gsd:plan-milestone-gaps 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 10d 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:plan-milestone-gaps — 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.

commands/plan-milestone-gaps.md · 35 lines

What it actually says

Reads MILESTONE-AUDIT.md, groups gaps into logical phases, creates phase entries in ROADMAP.md, and offers to plan each phase.

One command creates all fix phases — no manual /gsd:add-phase per gap.

<execution_context> @~/.claude/get-shit-done/workflows/plan-milestone-gaps.md </execution_context>

Original intent and current planning state are loaded on demand inside the workflow.

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. 10d ago First seen · 35 lines · 20 tokens per session scan A f2331cc5cf8d

Subscribe to this mod's changes

gsd:plan-milestone-gaps is a command published in the GitHub repository YousefNabil-SOC/claude-apex (2 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 261 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 89% identical to gsd:plan-milestone-gaps, differing in 8 lines, and is treated as a copy.