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 richkuo/rk-skills --skill milestone-workflowgit clone --depth 1 https://github.com/richkuo/rk-skillsWrote 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/richkuo/rk-skills/milestone-workflow)<a href="https://agentmods.dev/skills/richkuo/rk-skills/milestone-workflow"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/milestone-workflow/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/richkuo/rk-skills/milestone-workflow"><img src="https://agentmods.dev/badge/skills/richkuo/rk-skills/milestone-workflow.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00093 | $0.03914 |
| Opus 5.5 | $0.00037 | $0.01566 |
| Sonnet 5.5 | $0.00019 | $0.00783 |
| Haiku 4.5 | $0.00009 | $0.00391 |
Grade A, and why
milestone-workflow 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 2d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
milestone-workflow
No subagent holds merge authority: at each LGTM the run pauses as awaiting_merge; the session merges (step 5) and resumes with the merge in args.merged. Read-only table: milestoneplan.
Steps
1. Build the dependency tracks
Follow run-plan.md (Dependency tracks): build, resume, and skip buckets; cross-bucket edges; **Depends on:** (hard) and **Runs after:** (ordering-only) edges, inferred ones labeled; rejecting missing references, self-references, and cycles; out-of-milestone references. Tracks are { issues, after, runsAfter }; after and runsAfter hold 0-based track indices.
2. Present the run plan; approval is mandatory
Show the target branch (repo default, or the user's targetBranch, which also means no release), numbered tracks with titles (1-based display number beside each 0-based index), hard after edges separate from runsAfter edges, inferred edges, each issue's model/effort/plan (plan model: stamped, else Opus 5.5; plan effort: stamped, else high), whether keepStamps is on, the skipValidate set when the user gives one (per listed issue: the evidence source, session record or footer, and the predicted outcome: skip, or validates with the fallback reason from run-plan.md Preflight; for each footer issue, state that the prior validation's base branch and hard constraints are unknown and not carried), naming the harness on every Codex or Cursor CLI build or Codex CLI validate (cli-dispatch under an Opus 5.5 driver, never a substituted Claude run), the readiness boundary, and merge order. Do not invoke the Workflow tool until the user approves; approval is the multi-agent opt-in.
State the GitHub writes: issue-body corrections, plan comments, PRs, review comments, and, with merging on, squash-merges at LGTM plus green CI, branch deletion, issue closure, a docs-sync PR and its merge, a version-bump PR and its merge, and a release. Approval authorizes them; merge: false keeps merging manual.
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.
- 2d ago Changed 482dbbce59dc
- 19d ago Changed c03f34052ec3
- 20d ago Changed · +2 lines 02763df5b526
- 21d ago Changed 4977da324b0a
- 26d ago Changed · +1 lines · +93 tokens per session 0eae18079672
- 28d ago Changed e9f3e2a8d894
- 1mo ago Changed ad89474130c1
- 1mo ago Changed ede9c4dd7acc
- 1mo ago Changed · -29 lines 9beb17d9679c
- 1mo ago First seen · 80 lines · 0 tokens per session scan A 1682d0dc04f4
milestone-workflow is a skill published in the GitHub repository richkuo/rk-skills (50 stars, last pushed 2d ago), licensed MIT. It adds 93 tokens to every session and 3,914 once invoked, about $0.0004 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
issue-fields-migration
Bulk-migrate metadata to GitHub issue fields from two sources: repo labels (e.g. priority labels to a Priority field) and Project V2 fields. Use when users say "migrate my labels to issue fields", "migrate project fields to issue fields", "convert labels to issue fields", "copy project field values to issue fields"…
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.
factory-recover
Experimental workflow for finding and resuming interrupted coding runs. Use after an agent host restart or an interrupted automation.
comet-github-idea-to-issue
A workflow for turning a local idea, bug observation, or improvement proposal into a focused GitHub Issue draft. GitHub Issues are shared records for bugs, features, questions, and maintenance work.
codex-issue-coordinator
Coordinates a large batch of GitHub issues through separate Codex worker threads, tested pull requests, review loops, and gated merges. Use when the user asks one Codex thread to manage several coding sessions or complete a parent issue, milestone, or issue batch.