ms-confirm

ms-confirm is a command for coding agents from thixpin/pitway. It costs 0 tokens per session (308 once invoked), scanned A, a copy of milestone-confirm, MIT.

A command for approving a draft project milestone, or recording an approved change to its checking plan. A milestone is a defined piece of project work with agreed completion conditions.

In plain words
What is it for?
Use it to confirm a milestone after reviewing its contract, or to amend an already confirmed milestone when the agreed work or verification method changes.
Why use it?
It prevents work from starting before the developer has reviewed and explicitly accepted the plan. It also records later scope changes with approval.

Command

Install

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.

agentmods
npx agentmods add commands/thixpin/pitway/ms-confirm
Clone the repo
git clone --depth 1 https://github.com/thixpin/pitway

Wrote 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.

agentmods badge for ms-confirm

README.md
[![agentmods](https://agentmods.dev/badge/commands/thixpin/pitway/ms-confirm.svg)](https://agentmods.dev/commands/thixpin/pitway/ms-confirm)
Your own site
<a href="https://agentmods.dev/commands/thixpin/pitway/ms-confirm"><img src="https://agentmods.dev/badge/commands/thixpin/pitway/ms-confirm.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 308 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00308
Opus 5 $0.00000 $0.00154
Sonnet 5 $0.00000 $0.00062
Haiku 4.5 $0.00000 $0.00031

Measured 5d ago against content hash 9175defbdc11, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ms-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 5d 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.

Origin

This is a copy

100% identical to milestone-confirm — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

src/integrations/claude/commands/ms-confirm.md · 35 lines

What it actually says


description: PitWay: Confirm a draft milestone, or record an amended verification plan argument-hint:

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.

Changes

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.

  1. 5d ago First seen · 35 lines · 0 tokens per session scan A 9175defbdc11

Subscribe to this mod's changes

ms-confirm 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 308 tokens. A static security scan graded it A with 0 findings. It is 100% identical to milestone-confirm, differing in 0 lines, and is treated as a copy.