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 skills add Mathews-Tom/armory --skill milestone-runnergit clone --depth 1 https://github.com/Mathews-Tom/armoryWrote 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/skills/mathews-tom/armory/milestone-runner)<a href="https://agentmods.dev/skills/mathews-tom/armory/milestone-runner"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/milestone-runner/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/skills/mathews-tom/armory/milestone-runner"><img src="https://agentmods.dev/badge/skills/mathews-tom/armory/milestone-runner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 125 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 125 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00076 | $0.06481 |
| Opus 5.5 | $0.00030 | $0.02592 |
| Sonnet 5.5 | $0.00015 | $0.01296 |
| Haiku 4.5 | $0.00008 | $0.00648 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 290 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Milestone Runner
Run milestone prompts produced by plan-prompts. The runner coordinates mandatory design reconciliation, dependency-safe execution, verification, CI, review, merge/cleanup, and release preparation.
The runner executes existing prompts; it does not author a new product plan. It may require a docs-only reconciliation PR when the current plan no longer matches repository evidence. It invokes stacked-prs for stack topology. Only after a complete release train requires preparation does it hand the train's source-traceable release target to the release-captain agent, which edits the release artifacts and publishes them through ship-workflow only until the PR exists.
Core model
A milestone has two independent gates:
- Design gate. Before implementation, inspect the authoritative plan/prompt, current codebase, merged predecessor diffs, predecessor verification, CI, and local history. Require
DESIGN GOor stop onDESIGN NO-GO. - Merge gate. After implementation, require release-aware
GOplus external PR, CI, verification, and review evidence.
An ignored history ledger is reconstructible local evidence, not authoritative state. .docs/DEVELOPMENT_PLAN.md and .docs/EXECUTION_PROMPTS.md, merged PRs, CI, and current code remain authoritative.
Every terminal milestone result must print the literal heading NEXT STEPS: followed by concrete, ordered actions: the current milestone action, release-preparation state, and the next runnable milestone. A NO-GO must name remediation and either an independent milestone that can proceed or the reason no milestone can. A prose follow-up or JSON next_steps key is insufficient.
| Evidence | Use |
|---|---|
| Authoritative plan and prompts | Build the DAG, release trains, milestone contract, and design-gate scope. |
| Local history ledger | Carry prior gate decisions and verified outcomes; rebuild it when absent. |
| Current code plus merged predecessor diffs and PR evidence | Validate the plan’s assumptions, interfaces, dependencies, and acceptance. |
| CI/check state and verification commands | Confirm predecessor outcomes, reconciliation PRs, and implementation stacks. |
| Provider PR metadata | Confirm bases, reviewed reconciliation, stack topology, and merge state. |
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +26 lines 6134d0160dab
- 11d ago Changed · +1 lines e70d5abb07d6
- 1mo ago Changed · +35 lines 3e495fa5748b
- 1mo ago First seen · 228 lines · 76 tokens per session scan A f549e0a37e61
milestone-runner is a skill published in the GitHub repository Mathews-Tom/armory (337 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 6,481 once invoked, about $0.0003 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 skills, from other repositories
manager
A session-to-GitHub tracker that creates, updates, and reads issues across repositories, including their labels, parent epics, and project-board placement.
corp-new
A workflow for creating a new department folder inside a local agent headquarters, with its own rules, skills, tasks, and links back to the headquarters.
corp-doctor
A guided maintenance and setup tool for a Personal Corp system, meaning a business workflow built from AI agents, department repositories, and shared rules. It checks what exists before making changes.
gh-issues
Use when creating, searching, updating, or managing GitHub issues via CLI. Triggers: "issue", "create issue", "gh issue", "task tracking", "context", "handoff", "resume task", "session context", "save progress", "active tasks", "in-progress", "my tasks", "open issues". Covers: gh commands, bulk operations, JSON/jq…
retro
A structured weekly retrospective for a department. It reviews tasks and evidence from an ISO calendar week, then records findings and the next planning goal.
to-issues
Break a plan, spec, or PRD into independently-grabbable task files using tracer-bullet vertical slices.