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/thixpin/pitway/milestone-mergegit clone --depth 1 https://github.com/thixpin/pitwayWrote 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/thixpin/pitway/milestone-merge)<a href="https://agentmods.dev/commands/thixpin/pitway/milestone-merge"><img src="https://agentmods.dev/badge/commands/thixpin/pitway/milestone-merge.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.1 | $0.00013 | $0.00323 |
| Opus 5 | $0.00006 | $0.00161 |
| Sonnet 5 | $0.00003 | $0.00065 |
| Haiku 4.5 | $0.00001 | $0.00032 |
Grade A, and why
milestone-merge 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ms-merge — 100% identical, 0 lines differ
What it actually says
milestone-merge
Role: Main Agent
pitway milestone-merge <id> [--target <branch>] [--json]
Run after milestone-complete, once a milestone is completed: merges the
milestone's own branch into a target branch (default: the milestone's
base_branch). Refuses immediately, before any git mutation, unless the
milestone's status is completed.
Only meaningful under branch_strategy: milestone — a main-strategy
milestone (base_branch: null) commits directly to its base branch and has
no separate branch to merge; milestone-merge refuses with a named error
in that case.
Run it from the milestone's own branch (the natural position right after
milestone-complete), or from a branch it has already been merged into —
re-running it there is a safe, idempotent no-op (already-merged, no
duplicate merge commit). Running it from an unrelated branch or a detached
HEAD where the milestone's completion commit isn't reachable is refused by
name.
On a merge conflict, the attempt is aborted and rolled back automatically — it never leaves a half-merged working tree, and never auto-resolves. The original branch is always restored on any failure.
See ../protocol-driver.md. Run pitway milestone-merge --help for flags.
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 First seen · 36 lines · 13 tokens per session scan A c212e93eba0e
milestone-merge is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 4d ago), licensed MIT. It adds 13 tokens to every session and 323 once invoked, about $0.0001 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 commands, from other repositories
conventions-check
Check AGENTS.md, CLAUDE.md, and the projected agent artifacts (skills, subagents, commands) against the repo's conventions.
qux
Reference command fixture for the core pack.
deploy
Deploy command fixture at v0.1.
cmd
Alpha pack command fixture.
gjalla-log
Show recent semantic change history.
checklist
Generate a custom checklist for the current feature based on user requirements.