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/akougkas/wtf-p/wtfp-write-sectiongit 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-write-section)<a href="https://agentmods.dev/commands/akougkas/wtf-p/wtfp-write-section"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-write-section.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.1 | $0.00021 | $0.01066 |
| Opus 5 | $0.00010 | $0.00533 |
| Sonnet 5 | $0.00004 | $0.00213 |
| Haiku 4.5 | $0.00002 | $0.00107 |
Grade A, and why
wtfp:write-section 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 5d 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
88% identical to wtfp:execute-outline — 22 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a section
@${PLUGIN_ROOT}/project/README.md @${PLUGIN_ROOT}/skills/wtfp-write-section/SKILL.md @${PLUGIN_ROOT}/skills/wtfp-write-section/references/actions.md
Record contract
Read: project://manifest, project://config, project://state, project://decisions, project://structure/outline, project://sections/{section}, project://sections/{section}/context, project://sections/{section}/research, project://sections/{section}/plans/{plan}, project://sections/{section}/summary, project://sources/{source}, project://evidence/{evidence}, project://paper/{artifact}.
Produce: project://paper/{artifact} (create), project://paper/{artifact} (update), project://manifest (update), project://sections/{section}/summary (create), project://sections/{section}/summary (update), project://validations/{validation} (create), 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
- Require one approved plan and resolve all linked context, research, source/evidence records, decisions, prior summary, existing target, and necessary neighboring prose before choosing create or update.
- Draft only the declared manuscript artifact; cite only resolvable sources, preserve author constraints, and stop at blocking decisions.
- Read the persisted manuscript text back and calculate its actual body word count with one deterministic method; never copy a worker self-report, plan target, or summary count into project records. Validate the persisted draft against its plan and word budget.
- Create or update the required Markdown summary with that measured count, then read back both manuscript and summary. Missing, empty, or inconsistent output is a failed completion condition, not permission to link a path that does not exist.
- Persist the validation, synchronize the manuscript URI in
manifest.artifacts.manuscripts, and reconcile section/state records only after manuscript, summary, and validation readback succeeds. If blocked, create the declared checkpoint and stop; do not commit or merge 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.
- 5d ago First seen · 78 lines · 21 tokens per session scan A 30b8e0caee4f
wtfp:write-section is a command published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 6d ago), licensed MIT. It adds 21 tokens to every session and 1,066 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to wtfp:execute-outline, differing in 22 lines, and is treated as a copy.
Other commands, from other repositories
fd-execute
Implement plan.md with the TDD pipeline — parallel worktree guard from affect.md, wave-based execution, checkpoint after each wave.
fd-done
Close the task — summarize built vs required, then commit and push on confirmation.
fd-review
Two-lens review of the task artifacts before execution — CEO review challenges scope and premise, eng review checks architecture, edge cases, and blast radius.
fd-verify
Verify the implementation — run tests, check regression on affect.md files, review and scan; blocks /fd-done on failure.
fd-resume
Restore from checkpoint.json (falling back to STATE.md) — brief the user, PAUSE for confirmation, then continue from the recorded command and stage.
fd-checkpoint
Purpose: Force-save the current session to checkpoint.json and STATE.md so it can be safely resumed later with /fd-resume. Normally runs automatically on session.idle via the session-events hook; invoke manually to force a save before closing a session.