Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add akougkas/wtf-p/plugin install wtfpWrote 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/akougkas/wtf-p/resume-writing)<a href="https://agentmods.dev/commands/akougkas/wtf-p/resume-writing"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/resume-writing/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/akougkas/wtf-p/resume-writing"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/resume-writing.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00016 | $0.01056 |
| Opus 5.5 | $0.00006 | $0.00422 |
| Sonnet 5.5 | $0.00003 | $0.00211 |
| Haiku 4.5 | $0.00002 | $0.00106 |
Grade A, and why
resume-writing 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 29d 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.
This is a copy
83% identical to add-todo — 31 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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Resume writing
@${CLAUDE_PLUGIN_ROOT}/project/README.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-manage-project/SKILL.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-manage-project/references/actions.md
Record contract
Read: project://manifest, project://config, project://state, project://decisions, project://structure/outline, project://checkpoints/{checkpoint}, project://sections/{section}, project://sections/{section}/plans/{plan}, project://sections/{section}/reviews/{review}, project://sections/{section}/handoff, project://sections/{section}/summary, project://validations/{validation}, project://paper/{artifact}.
Produce: project://checkpoints/{checkpoint} (update), project://state (update).
Resolve every logical URI through the host adapter. Portable v1 JSON records are the source of truth: schema-validate before a write, preserve stable IDs, update revision and timestamps where required, and replace records atomically. Never pass a literal logical URI to a shell command or infer record state from a legacy Markdown control file.
Manuscript prose and supporting context, research, plan, review, summary, handoff, and deliverable artifacts retain their authored format (normally Markdown). Link them from the relevant v1 record; do not convert manuscript prose into project-state JSON.
Procedure
- In the current invocation, read and schema-validate the manifest, config, state, decisions, and every pending active checkpoint. Read the chosen pending checkpoint plus its linked handoff, section, selected plan, reviews, validations, manuscript, summary, and outline; a prior conversation, invocation prose, or generated report is not evidence that these reads occurred. Missing, stale, ambiguous, or conflicting resume inputs fail closed with zero writes.
- Verify referenced revisions and artifacts are current, then report completed work, pending work, blockers, stale assumptions, and the exact bounded options. Do not create a report artifact: before selection the action is read-only.
- Invoke the host's interactive user gate and wait for one exact option. Invocation arguments may request resumption but cannot answer this gate. If the gate is unavailable or no response is returned, report
needs-inputand make no mutation. - Only after the returned selection, resolve, waive, or expire the checkpoint as selected and set
state.statustoactivewhen continuation is confirmed. Preserve the existing validstate.phase, increment required revisions, and clear only the resolved active checkpoint URI. - Schema-validate and read back checkpoint and state before claiming success. Preserve the handoff until the selected continuation itself is confirmed.
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.
- 29d ago Changed 49a5bfd2ebc0
- 1mo ago First seen · 72 lines · 16 tokens per session scan A 9f41330ffae7
resume-writing is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 11d ago), licensed MIT. It adds 16 tokens to every session and 1,056 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 83% identical to add-todo, differing in 31 lines, and is treated as a copy.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
repo-architect
Repository structure optimization and multi-repo management with ruv-swarm coordination for scalable project architecture and development workflows.
project-stage-detect
Detect project phase and recommend actions.