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/chris-dare-dev/agent-kit/milestone-pipelinenpx skills add chris-dare-dev/agent-kit --skill milestone-pipelinegit clone --depth 1 https://github.com/chris-dare-dev/agent-kitWrote 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/chris-dare-dev/agent-kit/milestone-pipeline)<a href="https://agentmods.dev/skills/chris-dare-dev/agent-kit/milestone-pipeline"><img src="https://agentmods.dev/badge/skills/chris-dare-dev/agent-kit/milestone-pipeline.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.00088 | $0.03926 |
| Opus 5 | $0.00044 | $0.01963 |
| Sonnet 5 | $0.00018 | $0.00785 |
| Haiku 4.5 | $0.00009 | $0.00393 |
Grade A, and why
milestone-pipeline 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 4d 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 — 283 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex milestone pipeline adapter
This is a thin Codex orchestration adapter over the canonical pipeline command and shared deterministic scripts. It does not reimplement state or delivery semantics.
Invocation and discovery
Use:
$milestone-pipeline <ID> --repo-root "/absolute/path/to/target/repo" [--deep] [--resume]
Run Codex from the workspace root (default
$HOME/Work/workspace). Codex discovery stops at nested git roots, so starting in a
target repo may hide the workspace skill/agent pack. Every git command must use
git -C "$REPO_ROOT"; every pipeline script uses
$WS/.claude/scripts/.... Do not rely on the process CWD.
Set AGENT_KIT_ROOT to
$WS/<workspace>/<project>/agent-kit. Read these
canonical contracts completely before acting (references may be loaded by their
MCP names when available):
.claude/commands/milestone-pipeline.md.claude/references/milestone-pipeline-state-schema.md.claude/references/milestone-pipeline-artifacts-v2.md.claude/references/milestone-pipeline-agent-contract.md.claude/references/pipeline-pattern-v2.md
If state.json is v1/unversioned, stop normal execution and run the migration
preview. Never silently reinterpret legacy complete as live operation.
Legacy terminal/post-critique states re-enter critique-running, not closure or
operations. Apply migration only after presenting that downgrade.
The state freezes its pipeline-kit commit. If the installed writer has advanced,
run kit-upgrade-preview, show its exact old/new commit and writer hashes, and
run kit-upgrade --approved-by ... --scope-hash ... only after explicit human
approval. Never make old receipts silently inherit new semantics.
Codex collaboration mapping
The main Codex agent is the sole orchestrator and state writer. Subagents never spawn subagents and never advance phases.
- Claude
Agentfan-out maps to Codex collaboration agents spawned concurrently. - The current collaboration API may not expose a named custom-agent selector.
A task name is not role proof. Before every dispatch, load the canonical
data/agents/<role>.mdbody, persist a task-specific per-attempt body snapshot, include that snapshot in the task prompt, persist the exact prompt below the milestone artifact directory, and later record all hashes plus the actual non-null spawned task id inreview-manifest.json. In the current collaboration API,spawn_agentreturns a canonical task name such as/root/<safe-leaf>rather than a separate opaque id. Choose a globally unique leaf matching[a-z0-9][a-z0-9_]*before dispatch, verify the returned canonical name ends in exactly that leaf, and record that exact returned leaf asagent_task_id; do not sanitize, hash, or otherwise invent an identifier. The current harness has no signed receipt-verification endpoint, so this is prompt-enforced, tamper-evident provenance rather than a signed runtime identity or cryptographic execution proof. Stop if the runtime returns neither an opaque id nor the exact canonical task name/leaf pair. Use the exactMILESTONE_REVIEW_DISPATCH_V2header/body envelope defined inmilestone-pipeline-artifacts-v2.md; no free-form suffix may follow the body. - Use minimal/no inherited conversation for blind adversarial reviews. Supply only the canonical role body and explicit ID/repo/range/output inputs. Shared filesystem access means cryptographic blindness is unavailable; reviewers are nevertheless forbidden to read sibling critiques before their own output is complete.
- The generated Codex agent pack does not turn Claude
tools:frontmatter into a runtime sandbox. Read-only reviewer scope is prompt-enforced. Record target HEAD/status before dispatch and verify them again after every review wave; unexpected tracked-tree or ref mutation invalidates the wave and stops. - Wait for every required agent. A missing role, malformed return, timeout, or unavailable role body leaves the current phase running and stops the pipeline.
- Use worktrees only for parallel tracked-file mutation. Review/research agents operate in the shared target repo read-only and write only their assigned untracked artifact/critique output.
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.
- 4d ago First seen · 283 lines · 88 tokens per session scan A 0cdeb2ca7999
milestone-pipeline is a skill published in the GitHub repository chris-dare-dev/agent-kit (0 stars, last pushed 27d ago), licensed MIT. It adds 88 tokens to every session and 3,926 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…