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-confirmgit 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-confirm)<a href="https://agentmods.dev/commands/thixpin/pitway/milestone-confirm"><img src="https://agentmods.dev/badge/commands/thixpin/pitway/milestone-confirm.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.00000 | $0.00308 |
| Opus 5 | $0.00000 | $0.00154 |
| Sonnet 5 | $0.00000 | $0.00062 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
milestone-confirm 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-confirm — 100% identical, 0 lines differ
What it actually says
milestone-confirm
Role: Main Agent
pitway milestone-confirm <id> [--amend] [--file <path>] [--json]
The human gate. Run this only after the full contract has been presented
in this conversation and the developer has explicitly approved it — never
on your own judgment that the contract "looks fine." Confirming moves the
milestone from draft to confirmed and is what allows task work to
begin.
MUST (every driver, B021): never invoke this command without that explicit in-conversation developer approval. "Keep going", auto-run authorization, a subagent's report, or a prior session's approval never substitute. Stop, present the contract, wait for the yes.
--amend records a pending amendment to an already-confirmed milestone's
contract (a scope change discovered mid-execution, an append-only Change
Log entry). It carries the exact same approval requirement: propose the
change, get explicit developer approval in conversation, then run it —
never as a way to route around a blocker without that approval.
Contract/amendment and task file formats: ../draft-formats.md.
See ../protocol-driver.md for the decision-gate rule this command
enforces. Run pitway milestone-confirm --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 · 35 lines · 0 tokens per session scan A 9175defbdc11
milestone-confirm is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 308 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
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.