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-statusgit 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-status)<a href="https://agentmods.dev/commands/thixpin/pitway/milestone-status"><img src="https://agentmods.dev/badge/commands/thixpin/pitway/milestone-status.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.00000 | $0.00241 |
| Opus 5 | $0.00000 | $0.00120 |
| Sonnet 5 | $0.00000 | $0.00048 |
| Haiku 4.5 | $0.00000 | $0.00024 |
Grade A, and why
milestone-status 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 today.
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-status — 100% identical, 0 lines differ
What it actually says
milestone-status
Role: either (read-only)
pitway milestone-status [id] [--json]
Show a milestone's status, contract, progress, and tasks.
Without [id], show the active milestone or No active milestone.
With [id], show that milestone regardless of status.
The full status report is the default output. And show as human-readable and nice UI.
Read-only; never mutate state, dispatch tasks, or perform recovery.
When relaying the output, preserve the rendered table and racing footer as-is.
When any usage or reading is recorded, the token breakdown also lists one
line per role bucket (main / orchestrator / worker / auxiliary): measured
segments plus a missing count, and a count of recorded readings — readings
are never summed, and no line ever shows a milestone total or a percentage
(M047; docs/evidence/M042/synthesis.md, section 9).
See ../protocol-driver.md. Run pitway milestone-status --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.
- today Changed · +5 lines 0276f4de2a7d
- 4d ago First seen · 23 lines · 0 tokens per session scan A 1b14f082221c
milestone-status is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 241 tokens. 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
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.
cmd
Alpha pack command fixture.
gjalla-log
Show recent semantic change history.
implementar
Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.