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/checkpoint)<a href="https://agentmods.dev/commands/akougkas/wtf-p/checkpoint"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/checkpoint/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/checkpoint"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/checkpoint.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.00013 | $0.00968 |
| Opus 5.5 | $0.00005 | $0.00387 |
| Sonnet 5.5 | $0.00003 | $0.00194 |
| Haiku 4.5 | $0.00001 | $0.00097 |
Grade A, and why
checkpoint 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 — 33 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Manage checkpoints
@${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: the declared portable records and authored artifacts selected for the snapshot.
Produce: project://checkpoints/{checkpoint} (create), project://archives/checkpoints/{checkpoint} (create), project://archives/recovery/{artifact} (create on restore), project://manifest (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
- For save, select concrete contained resources, copy their exact bytes into an immutable checkpoint archive, hash every entry, then create a non-blocking
state-snapshotcheckpoint that records the archive URI, logical resource URIs, record revisions, and SHA-256 values. Link the archive from the manifest and read everything back before success. - For list or inspect, report snapshot scope and verify that the archive, resources, revisions, and hashes still resolve without mutation.
- For restore, compare the selected snapshot with current resources, create and verify a pre-restore recovery archive, preview the exact replacements, and require a separate authorization immediately before applying them. Restore only snapshot-declared resources atomically, schema-validate records, verify hashes, and mark the checkpoint restored. Never use a commit, tag, checkout, reset, or branch movement as checkpoint storage.
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 848af0567985
- 1mo ago First seen · 74 lines · 13 tokens per session scan A db8fce47bba7
checkpoint is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 11d ago), licensed MIT. It adds 13 tokens to every session and 968 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 33 lines, and is treated as a copy.
Other commands, from other repositories
dashboard-session-unhide
Unhide a previously hidden session. Usage /dashboard:session-unhide.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
start
First-time onboarding — guided setup.
me-cfd-review
Review thermal-fluid CFD setup, boundary conditions, mesh, wall treatment, convergence, validation, and whether the claims are supported.
research
Start or resume an academic research project — idea through literature, methodology, writing, feedback, and publishing.
setup_research_plan
Set up or start a research project.