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-completegit clone --depth 1 https://github.com/thixpin/pitwayWhat 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.00015 | $0.00206 |
| Opus 5 | $0.00008 | $0.00103 |
| Sonnet 5 | $0.00003 | $0.00041 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
milestone-complete 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 3d 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-complete — 100% identical, 0 lines differ
What it actually says
milestone-complete
Role: Main Agent
pitway milestone-complete <id> [--json]
The terminal step: run it once every task is completed and every
verification check has passed. It's what actually closes the milestone out
— don't treat a milestone as done, or tell the developer it's done, until
this has run successfully.
Its human-mode output ends with: Run 'pitway milestone-merge <id>' only with separate, explicit developer approval -- it is never run automatically. Under branch_strategy: milestone, that is the actual next
step — but never run milestone-merge on the strength of this completion
alone; wait for the developer to separately ask for it, exactly as stated.
(--json output does not carry this sentence.)
See ../protocol-driver.md.
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.
- 3d ago First seen · 27 lines · 0 tokens per session scan A 2e983056267a
milestone-complete is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 206 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
pause
仅本 session 暂停 PACEflow 流程门（session 结束自动失效，artifact 保护保留）.
disable
在当前项目停用 PACEflow（不删除任何 artifact，随时可恢复）.
enable
在当前项目启用 PACEflow（首次启用会引导选择 artifact 存放位置）.
resume
恢复本 session 的 PACEflow（删除 pause 标志）.
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.