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/auto-rungit 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.00011 | $0.00340 |
| Opus 5 | $0.00005 | $0.00170 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
auto-run 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 3d 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
auto-run
Role: Main Agent (enable, disable) · either (status)
pitway auto-run enable [milestone-id] [--json]
pitway auto-run disable [milestone-id] [--json]
pitway auto-run status [milestone-id] [--json]
Manages auto-run authorization only — it never dispatches, executes, or
transitions a task itself. Authorization is a milestone-scoped fact, derived
purely from enable/disable records and the milestone's own journal
history; nothing here runs a task loop.
enable [milestone-id] requires the milestone be in_progress and records
its current verification_approved_hash; re-running it while still
authorized against that same hash is a safe no-op. disable [milestone-id]
and status [milestone-id] both work for a milestone in any status.
You call enable only when the developer selects Auto-run at the task
continuation prompt, and status before every auto-continued step —
necessary but never sufficient on its own. See ../interactive-ux.md for
the full decision UX and the live checks that sit alongside status, and
../protocol-driver.md for how this fits the rest of the driver protocol.
Run pitway auto-run --help or pitway auto-run <subcommand> --help for flags and details.
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.
- 3d ago First seen · 32 lines · 0 tokens per session scan A 611a07fb5027
auto-run is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 340 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.