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/audit-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/audit-milestone)<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/audit-milestone"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/audit-milestone.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.1 | $0.00017 | $0.01689 |
| Opus 5 | $0.00009 | $0.00844 |
| Sonnet 5 | $0.00003 | $0.00338 |
| Haiku 4.5 | $0.00002 | $0.00169 |
Grade A, and why
gsd:audit-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 6d 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:audit-milestone — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This command IS the orchestrator. Reads existing VERIFICATION.md files (phases already verified during execute-phase), aggregates tech debt and deferred gaps, then spawns integration checker for cross-phase wiring.
<execution_context>
</execution_context>
Original Intent: @.planning/PROJECT.md @.planning/REQUIREMENTS.md
Planned Work: @.planning/ROADMAP.md @.planning/config.json (if exists)
Completed Work: Glob: .planning/phases//-SUMMARY.md Glob: .planning/phases//-VERIFICATION.md
0. Resolve Model Profile
Read model profile for agent spawning:
MODEL_PROFILE=$(cat .planning/config.json 2>/dev/null | grep -o '"model_profile"[[:space:]]*:[[:space:]]*"[^"]*"' | grep -o '"[^"]*"$' | tr -d '"' || echo "balanced")
Default to "balanced" if not set.
Model lookup table:
| Agent | quality | balanced | budget |
|---|---|---|---|
| gsd-integration-checker | sonnet | sonnet | haiku |
Store resolved model for use in Task call below.
1. Determine Milestone Scope
# Get phases in milestone
ls -d .planning/phases/*/ | sort -V
- Parse version from arguments or detect current from ROADMAP.md
- Identify all phase directories in scope
- Extract milestone definition of done from ROADMAP.md
- Extract requirements mapped to this milestone from REQUIREMENTS.md
2. Read All Phase Verifications
For each phase directory, read the VERIFICATION.md:
cat .planning/phases/01-*/*-VERIFICATION.md
cat .planning/phases/02-*/*-VERIFICATION.md
# etc.
From each VERIFICATION.md, extract:
- Status: passed | gaps_found
- Critical gaps: (if any — these are blockers)
- Non-critical gaps: tech debt, deferred items, warnings
- Anti-patterns found: TODOs, stubs, placeholders
- Requirements coverage: which requirements satisfied/blocked
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.
- 6d ago First seen · 278 lines · 17 tokens per session scan A bab0f734b972
gsd:audit-milestone is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 29d ago), licensed MIT. It adds 17 tokens to every session and 1,689 once invoked, about $0.0001 per session on Opus 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.
hatch3r-board-fill
Create epics and issues/work items from todo.md, reorganize the board with dependency analysis, readiness assessment, and implementation ordering. Supports GitHub, Azure DevOps, and GitLab.
hatch3r-feature-plan
Design a new capability -- draft user stories, acceptance criteria, data model, API surface, and sub-issue breakdown as an epic-shaped todo.md for greenfield features.
hatch3r-roadmap
Sequence delivery phases over time into a dependency-ordered milestone plan with business and technical lenses, emitting a todo.md rollout schedule rather than design docs.
hatch3r-board-pickup
Pick up epics/issues from the project board: dependency-aware selection, collision detection, branching, batch execution. Multi-platform.