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-execute-outline)<a href="https://agentmods.dev/commands/akougkas/wtf-p/wtfp-execute-outline"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-execute-outline/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-execute-outline"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-execute-outline.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.00018 | $0.00915 |
| Opus 5 | $0.00009 | $0.00458 |
| Sonnet 5 | $0.00004 | $0.00183 |
| Haiku 4.5 | $0.00002 | $0.00092 |
Grade A, and why
wtfp:execute-outline 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 9d 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- wtfp:plan-section — 94% identical, 26 lines differ
- wtfp:submit-milestone — 88% identical, 27 lines differ
- wtfp:write-section — 88% identical, 22 lines differ
- wtfp:plan-milestone-gaps — 86% identical, 37 lines differ
- wtfp:plan-revision — 84% identical, 37 lines differ
- wtfp:list-assumptions — 84% identical, 40 lines differ
- wtfp:progress — 83% identical, 27 lines differ
- wtfp:insert-section — 83% identical, 39 lines differ
How it starts
The opening of the file, as written. The whole thing — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execute the outline
@${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}/plans/{plan}, project://sections/{section}/summary, project://sources/{source}, project://evidence/{evidence}, project://checkpoints/{checkpoint}, project://paper/{artifact}.
Produce: project://paper/{artifact} (update), project://sections/{section}/summary (create), project://sections/{section}/summary (update), project://checkpoints/{checkpoint} (create), project://checkpoints/{checkpoint} (update), project://sections/{section} (update), project://state (update), project://validations/{validation} (create).
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
- Build waves from outline dependencies and select only sections with approved plans.
- Within configured parallelism, delegate bounded section work grounded in source/evidence records; create or update summaries, serialize overlapping outputs, and create or reconcile blocking checkpoints before dependent work proceeds.
- After each wave, validate outputs and reconcile section/state records from actual artifacts. Do not create branches or commits.
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.
- 9d ago First seen · 76 lines · 18 tokens per session scan A 1efad280f56e
wtfp:execute-outline is a command published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 10d ago), licensed MIT. It adds 18 tokens to every session and 915 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
retro
Reflect on the current research session and collect improvement suggestions.
setup_research_plan
Set up or start a research project.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.