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.
git clone --depth 1 https://github.com/akougkas/wtf-pWrote 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/wtfp-pause-writing)<a href="https://agentmods.dev/commands/akougkas/wtf-p/wtfp-pause-writing"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-pause-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/wtfp-pause-writing"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-pause-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.00022 | $0.00855 |
| Opus 5 | $0.00011 | $0.00428 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
wtfp:pause-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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pause writing
@${PLUGIN_ROOT}/project/README.md @${PLUGIN_ROOT}/skills/wtfp-manage-project/SKILL.md @${PLUGIN_ROOT}/skills/wtfp-manage-project/references/actions.md
Record contract
Read: project://state, project://decisions, project://structure/outline, project://sections/{section}, project://sections/{section}/plans/{plan}, project://sections/{section}/reviews/{review}, project://sections/{section}/summary, project://sections/{section}/handoff, project://validations/{validation}, project://paper/{artifact}.
Produce: project://sections/{section}/handoff (create), project://sections/{section}/handoff (update), project://checkpoints/{checkpoint} (create), project://sections/{section} (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
- Reconcile current state, decisions, outline revision, section plan, manuscript, summary, reviews, and validations; identify completed work, pending work, blockers, and the next action.
- Write a Markdown handoff artifact for narrative continuity plus a human-action checkpoint for machine-readable resumption.
- Link the handoff from
section.artifacts.handoffand the checkpoint fromsection.checkpoint_uris, then setstate.statustopausedand link the checkpoint fromstate.active_checkpoint_uris. Preservestate.phase, progress, and current section; pausing changes status, checkpoint linkage, revision, and timestamp only.pausedis a status and is never a phase. Do not commit automatically.
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.
- 10d ago First seen · 66 lines · 22 tokens per session scan A 616d9385afda
wtfp:pause-writing is a command published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 10d ago), licensed MIT. It adds 22 tokens to every session and 855 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
deja
Search this machine's past AI coding sessions (deja-vu).
dashboard-session-tell
Send a prompt to another session. Usage /dashboard:session-tell.
dashboard-session-list
List all pi sessions (id, status, name, cwd). Runs locally, no LLM.
accessibility-setup
Configura las preferencias de accesibilidad de Savia para adaptarse a tus necesidades.
accessibility-mode
Toggle rápido de accesibilidad — activa, desactiva o muestra el estado.
seo-meta
Reviews and generates optimized meta titles and descriptions for all pages. Checks length, keywords, uniqueness and potential CTR. TRIGGER when the user enters /seo-meta or asks to review, improve or generate meta tags, title tags or meta descriptions.