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 skills/mathews-tom/armory/milestone-runnernpx 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.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.00076 | $0.03241 |
| Opus 5 | $0.00038 | $0.01621 |
| Sonnet 5 | $0.00015 | $0.00648 |
| Haiku 4.5 | $0.00008 | $0.00324 |
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 — 228 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 and ship-workflow only after a complete release train requires preparation.
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.
- 5d 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 (316 stars, last pushed 7d ago), licensed MIT. It adds 76 tokens to every session and 3,241 once invoked, about $0.0004 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 skills, from other repositories
openagentskill-registry
Discover, compare, audit, and safely install reusable AI Agent Skills with OpenAgentSkill. Use whenever an agent needs a capability it does not already have, must compare Skill alternatives, or needs evidence before installing third-party instructions.
manager
Sync session work into GitHub issues, or query track status across repos. Write: find/update issue + W-label. Read: "что по ". Triggers: "создай issue", "синкни сессию", "manager". Not day/week plans (daily-tasks).
weekly-retro
Use when the user is closing an ISO week, reviewing planned outcomes against evidence, interviewing work Areas, resolving unfinished commitments, or asking for "ретро", "weekly retro", "week review", or lessons from the week.
art-director
Orchestrate iterative visual style searches with branch prompts, decision graphs, feedback loops, and final direction selection.
corp-doctor
Use when a Personal Corp operating loop needs setup, repair, a new department, or task routing: HQ files and agent rules, GitHub issue workflow, corp- owner map, department repositories, or deciding which repo an issue belongs to. Triggers: "corp doctor", "почини контур", "заведи отдел", "куда положить задачу"…
html-draft
Use when user wants a standalone HTML diagram in flat engineering blueprint style — architecture diagrams, system flows, technical spec sheets, component maps. Generates one HTML file using Tailwind v4 (browser CDN) for layout and D3 v7 (CDN) for SVG diagrams. User-invoked only — do NOT auto-trigger. Triggers on…