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/minhoyoo-iotrust/claude-plugin/milestone-runnergit clone --depth 1 https://github.com/minhoyoo-iotrust/claude-pluginWrote 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/minhoyoo-iotrust/claude-plugin/milestone-runner)<a href="https://agentmods.dev/commands/minhoyoo-iotrust/claude-plugin/milestone-runner"><img src="https://agentmods.dev/badge/commands/minhoyoo-iotrust/claude-plugin/milestone-runner.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 | $0.00036 | $0.02704 |
| Opus 5 | $0.00018 | $0.01352 |
| Sonnet 5 | $0.00007 | $0.00541 |
| Haiku 4.5 | $0.00004 | $0.00270 |
Grade A, and why
milestone-runner 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 358 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CRITICAL INSTRUCTION: Do NOT use the Skill tool to invoke gsdu:milestone-runner. Do NOT re-invoke this command. All workflow steps are below — execute them directly.
For each PLANNED objective: new-milestone → autopilot → complete-milestone → PR → CI → merge → pull base branch.
Orchestrator stays lean. Each milestone phase is delegated via existing GSD skills.
Prerequisites:
- GSD must be installed (
~/.claude/get-shit-done/exists) - Objective documents with
status: PLANNEDin frontmatter ghCLI authenticated for PR/merge operations
If --base <branch> argument is provided, use that value. Otherwise, auto-detect the repo's default branch:
BASE_BRANCH=$(gh repo view --json defaultBranch -q '.defaultBranch')
echo "BASE_BRANCH=${BASE_BRANCH}"
Store BASE_BRANCH for use throughout the workflow. All subsequent references to the target branch use ${BASE_BRANCH}.
# Check GSD installation
test -f "$HOME/.claude/get-shit-done/bin/gsd-tools.cjs" || echo "GSD_NOT_FOUND"
# Check gh CLI
gh auth status 2>&1 | head -3
If GSD_NOT_FOUND:
GSD is not installed. Install it first:
https://github.com/gsd-build/get-shit-done
Exit.
2. Determine objectives directory:
Use --objectives <dir> argument if provided, otherwise objectives/.
ls ${OBJECTIVES_DIR}/*.md 2>/dev/null
If no files found, exit with error.
3. Scan for PLANNED objectives:
Read each .md file in the objectives directory. Parse YAML frontmatter for status: PLANNED.
Build execution queue:
- Filter: only
status: PLANNEDdocuments - Sort: by filename ascending (natural order)
- If
--from <prefix>given: skip files before the matching prefix
For each objective, extract:
filename— e.g.,m01-26-brave-search-integration.mdtitle— first#heading in the documentversion— extract from frontmatterversionfield if present; otherwise derive from filename pattern:- Pattern
m{major}-{minor}-*→v{major}.{minor}(e.g.,m01-26-*→v1.26) - Pattern
v{version}-*→ use as-is - If no pattern matches: report error and ask user
- Pattern
slug— derive from filename (strip prefix and extension, kebab-case)content— full file content (for milestone context)
If queue is empty:
No PLANNED objectives found in ${OBJECTIVES_DIR}/.
All objectives may already be SHIPPED or IN_PROGRESS.
Exit.
## Milestone Runner — Execution Plan
| # | Filename | Version | Title |
|---|----------|---------|-------|
| 1 | m01-26-brave-search-integration.md | v1.26 | 시장 데이터 파운데이션 |
| 2 | m01-27-market-analysis-engine.md | v1.27 | 시장 분석 엔진 |
| ... | ... | ... | ... |
**Steps per milestone:**
1. Write MILESTONE-CONTEXT.md from objective content
2. /gsd:new-milestone (version + context)
3. /gsdu:autopilot
4. /gsd:complete-milestone
5. Create PR → Wait CI → Merge (--merge) → Checkout ${BASE_BRANCH} → Pull
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.
- 5d ago First seen · 358 lines · 36 tokens per session scan A 10b396827898
milestone-runner is a command published in the GitHub repository minhoyoo-iotrust/claude-plugin (5 stars, last pushed 4mo ago), licensed MIT. It adds 36 tokens to every session and 2,704 once invoked, about $0.0002 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-31.
Other commands, from other repositories
commit-push-pr
Commit, push, and open a PR.
speckit.aftercode
Automatically execute the subsequent code delivery pipeline: skilltypesync → changelog → commit → prgenerate, in strict sequential order.
commit
Automatically generate commit message based on changes and push to current branch. Analyzes git diff to create meaningful commit following conventional commits format. Optionally creates and pushes a git tag.
changelog-update
Actualiza CHANGELOG.md automáticamente analizando los commits desde la última versión/release. Clasifica los cambios por tipo (feat, fix, docs, etc.) usando los commits convencionales del workspace. Opcionalmente sugiere bump de versión semántica. Delega la redacción final a tech-writer.
changelog-auto
Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…
publish-essay
Create MDX file, commit to id8labs-hub repo, and trigger Vercel deploy.