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/verifygit 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.00015 | $0.00260 |
| Opus 5 | $0.00008 | $0.00130 |
| Sonnet 5 | $0.00003 | $0.00052 |
| Haiku 4.5 | $0.00002 | $0.00026 |
Grade A, and why
verify 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 2d 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.
What it actually says
verify
Role: Orchestrator (runs, --check records) · either (--status)
pitway verify [id] [--status] [--json]
pitway verify [id] --check <ctid> [--json]
pitway verify [id] --check <ctid> --pass|--fail --evidence <text> [--json]
Runs the milestone's approved command checks and records the results;
--check <id> --pass|--fail --evidence <text> records a manual/review
check a human (or you, on the human's behalf, for a review-type check)
had to actually evaluate. Only ever runs the commands approved at
milestone-confirm time (verification_approved_hash) — never an
agent-authored command that wasn't part of that approval.
Use it once every task in a milestone is done, to check the milestone's
acceptance criteria as a whole before milestone-complete.
See ../protocol-driver.md. Run pitway verify --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.
- 2d ago First seen · 27 lines · 0 tokens per session scan A f25a28e38b63
verify is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 3d ago), licensed MIT. It adds 15 tokens to every session and 260 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 存放位置）.
conventions-check
Check AGENTS.md, CLAUDE.md, and the projected agent artifacts (skills, subagents, commands) against the repo's conventions.
resume
恢复本 session 的 PACEflow（删除 pause 标志）.
qux
Reference command fixture for the core pack.