Borrowing it
Nothing to install: this file belongs to GeoloeG-IsT/agents-reverse-engineer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/GeoloeG-IsT/agents-reverse-engineer/main/.claude/commands/gsd/new-milestone.mdgit clone --depth 1 https://github.com/GeoloeG-IsT/agents-reverse-engineerWrote 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/geoloeg-ist/agents-reverse-engineer/new-milestone)<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/new-milestone"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/new-milestone/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.
<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/new-milestone"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/new-milestone.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00020 | $0.04714 |
| Opus 5.5 | $0.00008 | $0.01886 |
| Sonnet 5.5 | $0.00004 | $0.00943 |
| Haiku 4.5 | $0.00002 | $0.00471 |
Grade A, and why
gsd:new-milestone 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 1mo 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- gsd:new-milestone — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 722 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This is the brownfield equivalent of new-project. The project exists, PROJECT.md has history. This command gathers "what's next", updates PROJECT.md, then continues through the full requirements → roadmap cycle.
Creates/Updates:
.planning/PROJECT.md— updated with new milestone goals.planning/research/— domain research (optional, focuses on NEW features).planning/REQUIREMENTS.md— scoped requirements for this milestone.planning/ROADMAP.md— phase structure (continues numbering).planning/STATE.md— reset for new milestone
After this command: Run /gsd:plan-phase [N] 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>
Load project context: @.planning/PROJECT.md @.planning/STATE.md @.planning/MILESTONES.md @.planning/config.json
Load milestone context (if exists, from /gsd:discuss-milestone): @.planning/MILESTONE-CONTEXT.md
Phase 1: Load Context
- Read PROJECT.md (existing project, Validated requirements, decisions)
- Read MILESTONES.md (what shipped previously)
- Read STATE.md (pending todos, blockers)
- Check for MILESTONE-CONTEXT.md (from /gsd:discuss-milestone)
Phase 2: Gather Milestone Goals
If MILESTONE-CONTEXT.md exists:
- Use features and scope from discuss-milestone
- Present summary for confirmation
If no context file:
- Present what shipped in last milestone
- Ask: "What do you want to build next?"
- Use AskUserQuestion to explore features
- Probe for priorities, constraints, scope
Phase 3: Determine Milestone Version
- Parse last version from MILESTONES.md
- Suggest next version (v1.0 → v1.1, or v2.0 for major)
- Confirm with user
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.
- 1mo ago First seen · 722 lines · 20 tokens per session scan A 44f31ef8d45a
gsd:new-milestone is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (22 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 4,714 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
pulse-check
Pulse and worker utilisation diagnostics across repos.json, with self-improvement recommendations.
runners-check
../../workflows/runners-check.md.
story-6.1.4
Story ID: 6.1.4 Epic: Epic-6.1 - Agent Identity System Wave: Wave 1 (Foundation) Status: 📋 Ready to Start Priority: 🔴 Critical Owner: Dev (Dex) Created: 2025-01-14 Updated: 2025-01-17 (v4 - Unified System Integration) Duration: 2.5 days (20 hours) Investment: $250.00.
route
../../workflows/route.md.
runners
../../workflows/runners.md.
save-todo
../../workflows/save-todo.md.