ms-cancel

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

A command for permanently abandoning a draft milestone, where a milestone is a tracked piece of project work. It changes the draft's status to cancelled while keeping its directory and contract file.

In plain words
What is it for?
Use it only for draft milestones that should be abandoned permanently; use the replacement option when the draft merely needs correction.
Why use it?
It prevents an abandoned draft's identifier from being reused and clearly separates true abandonment from simply correcting a mistake.

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-cancel
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-cancel

README.md
[![agentmods](https://agentmods.dev/badge/commands/thixpin/pitway/ms-cancel.svg)](https://agentmods.dev/commands/thixpin/pitway/ms-cancel)
Your own site
<a href="https://agentmods.dev/commands/thixpin/pitway/ms-cancel"><img src="https://agentmods.dev/badge/commands/thixpin/pitway/ms-cancel.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 419 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.00419
Opus 5 $0.00000 $0.00210
Sonnet 5 $0.00000 $0.00084
Haiku 4.5 $0.00000 $0.00042

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

Security

Grade A, and why

ms-cancel 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 4d 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-cancel — 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-cancel.md · 40 lines

What it actually says


description: PitWay: Permanently abandon a draft milestone; the id is never reused argument-hint:

milestone-cancel

Role: Main Agent

pitway milestone-cancel <id> [--json]

Use to permanently abandon a draft milestone — genuine abandonment, not a routine correction. Only works while the milestone is still draft; the directory and contract.md are preserved (status becomes cancelled) and the id is never reused. No git operation occurs.

If the draft just has a mistake in it, use milestone-add --replace <id> instead — that corrects it in place under the same id without burning it.

Confirmed-milestone boundary: milestone-cancel never applies once a milestone is confirmed/in_progress, by design. in_progress genuinely has no -> cancelled edge in the state machine (state-machine.ts); a persisted confirmed status technically does list one, but confirmed is never an observable resting status in practice — milestone-confirm collapses draft -> confirmed -> in_progress into one persisted write, so there is no real window in which a milestone sits at confirmed for this command to act on. To abandon remaining work in an already-confirmed milestone: cancel the individual not-yet-started tasks (task-update <id> cancelled, valid from planned/waiting/ready) and complete the milestone with whatever required tasks are actually done. Never git reset/rewrite history to undo a confirmed milestone or a completed task — that is exactly the class of destructive action PitWay's git-safety rules exist to prevent. Adding corrective or follow-on work the other direction — mid-flight, without a new milestone — is task-add's job; see commands/task-add.md.

See ../protocol-driver.md.

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. 4d ago First seen · 40 lines · 0 tokens per session scan A c317f888574d

Subscribe to this mod's changes

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