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/resumegit clone --depth 1 https://github.com/thixpin/pitwayWrote 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.
[](https://agentmods.dev/commands/thixpin/pitway/resume)<a href="https://agentmods.dev/commands/thixpin/pitway/resume"><img src="https://agentmods.dev/badge/commands/thixpin/pitway/resume.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00017 | $0.00338 |
| Opus 5 | $0.00009 | $0.00169 |
| Sonnet 5 | $0.00003 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
resume 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.
What it actually says
resume
Role: either (read-only)
pitway resume [--json]
Run this first in any session where you're not already certain what
PitWay's state is — a fresh conversation, after a context reset, after
picking the project back up. It reconstructs workflow state from
.pitway/ and recommends the next task, so you never have to guess or
reconstruct that by reading .pitway/ files yourself (which you must
never do — see ../protocol-driver.md).
Configuration drift. resume also reports, for each driver already
installed in the project (its destination directory exists), whether any
of its managed assets differ from the version PitWay currently ships
(classifyDriverAssets — the same comparison init itself uses). When
at least one installed driver has drifted, resume shows the affected
driver(s) and exactly one command to run: pitway init --reconfigure,
with --no-claude appended only when .claude/ isn't present (so the
suggested command can't silently install Claude into a project that
opted out). This is advisory only — resume never runs init itself
and never blocks. A drifted asset may be a deliberate local edit or
simply a stale shipped version; PitWay has no way to tell which, so it
reports that the asset differs, never why.
See ../protocol-driver.md.
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.
- 4d ago First seen · 34 lines · 0 tokens per session scan A e79938190358
resume is a command published in the GitHub repository thixpin/pitway (19 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 338 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
trellis-finish-work
Wrap up the current session: archive the active task (and any other completed-but-unarchived tasks the user wants to clean up) and record the session journal. Code commits are NOT done here — those happen in workflow Phase 3.4 before you invoke this command.
resume-project
Cold-start project — BOARD, PROGRESS, stalled tasks, worktrees.
feature-track-init
Initialize Feature Track in this repository.
work
Work unit management: list, continue, checkpoint, switch.
resume
恢复本 session 的 PACEflow（删除 pause 标志）.
recap
Summarize what happened in the project since a given date. Produces a short lead on what's different now, backed by tables and lists covering completed work, state changes, backlog movement, and key decisions. Use when the user wants to catch up on project activity, review recent progress, or generate a status update…