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/geoloeg-ist/agents-reverse-engineer/plan-milestone-gapsgit 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/plan-milestone-gaps)<a href="https://agentmods.dev/commands/geoloeg-ist/agents-reverse-engineer/plan-milestone-gaps"><img src="https://agentmods.dev/badge/commands/geoloeg-ist/agents-reverse-engineer/plan-milestone-gaps.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.00020 | $0.01826 |
| Opus 5 | $0.00010 | $0.00913 |
| Sonnet 5 | $0.00004 | $0.00365 |
| Haiku 4.5 | $0.00002 | $0.00183 |
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 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:plan-milestone-gaps — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 296 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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>
</execution_context>
Original intent (for prioritization): @.planning/PROJECT.md @.planning/REQUIREMENTS.md
Current state: @.planning/ROADMAP.md @.planning/STATE.md
1. Load Audit Results
# Find the most recent audit file
ls -t .planning/v*-MILESTONE-AUDIT.md 2>/dev/null | head -1
Parse YAML frontmatter to extract structured gaps:
gaps.requirements— unsatisfied requirementsgaps.integration— missing cross-phase connectionsgaps.flows— broken E2E flows
If no audit file exists or has no gaps, error:
No audit gaps found. Run `/gsd:audit-milestone` first.
2. Prioritize Gaps
Group gaps by priority from REQUIREMENTS.md:
| Priority | Action |
|---|---|
must |
Create phase, blocks milestone |
should |
Create phase, recommended |
nice |
Ask user: include or defer? |
For integration/flow gaps, infer priority from affected requirements.
3. Group Gaps into Phases
Cluster related gaps into logical phases:
Grouping rules:
- Same affected phase → combine into one fix phase
- Same subsystem (auth, API, UI) → combine
- Dependency order (fix stubs before wiring)
- Keep phases focused: 2-4 tasks each
Example grouping:
Gap: DASH-01 unsatisfied (Dashboard doesn't fetch)
Gap: Integration Phase 1→3 (Auth not passed to API calls)
Gap: Flow "View dashboard" broken at data fetch
→ Phase 6: "Wire Dashboard to API"
- Add fetch to Dashboard.tsx
- Include auth header in fetch
- Handle response, update state
- Render user data
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 · 296 lines · 20 tokens per session scan A 5041637d3519
gsd:plan-milestone-gaps is a command published in the GitHub repository GeoloeG-IsT/agents-reverse-engineer (20 stars, last pushed 29d ago), licensed MIT. It adds 20 tokens to every session and 1,826 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
setup-git
/setup-git is per-repo platform secret setup — most importantly SYNCPAT, the fine-grained PAT that allows the issue-sync workflow to author issues as the maintainer instead of as github-actions[bot]. Without SYNCPAT, every synced issue carries authorassociation: NONE and the t2449 worker-briefed auto-merge gate…
auto-reason
Subjective self-refinement with blind judging, Borda aggregation, and provider-agnostic model routing.
deep-research
Deep research — produce a cited decision-grade research report and artifact bundle.
goals
Goal-oriented mission entrypoint — set, view, or drive long-running objectives through the mission system.
report-render
Render report-ready Markdown or JSON to HTML and PDF-ready previews.
vault
Manage aidevops Vault setup, lock state, encrypted sync, fleet trust, and protected-data dispatch metadata.