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/task-discardgit 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.00013 | $0.00278 |
| Opus 5 | $0.00006 | $0.00139 |
| Sonnet 5 | $0.00003 | $0.00056 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
task-discard 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 yesterday.
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.
What it actually says
task-discard
Role: Orchestrator
pitway task-discard <id> --reason <text> [--json]
Abandons one dispatched task's worktree without integrating — the single
sanctioned exit besides task-integrate for a live dispatch. Requires an
explicit --reason <text>. Appends a worktree_discard journal record
(reason + discarded branch HEAD SHA when still resolvable, evidence-only),
removes the worktree and scaffolding branch (tolerating an
already-vanished worktree), and transitions the task in_progress → failed through the existing state machine — whence failed → ready
allows a fresh dispatch, with attempts accumulating.
Discarded work is unrecoverable through PitWay. Never discard in an
integrate crash window (cleanup pending, or an applied-but-unrecorded
diff): the work is already recorded or applied in the main tree —
re-running task-integrate <id> finishes it. pitway resume names those
states read-only.
See ../protocol-driver.md (Parallel dispatch). Run pitway task-discard --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.
- yesterday First seen · 31 lines · 0 tokens per session scan A 79da77dbeb8d
task-discard is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 278 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.