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 skills add akougkas/wtf-p --skill wtfp-plan-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/skills/akougkas/wtf-p/wtfp-plan-section)<a href="https://agentmods.dev/skills/akougkas/wtf-p/wtfp-plan-section"><img src="https://agentmods.dev/badge/skills/akougkas/wtf-p/wtfp-plan-section/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/skills/akougkas/wtf-p/wtfp-plan-section"><img src="https://agentmods.dev/badge/skills/akougkas/wtf-p/wtfp-plan-section.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.00076 | $0.00616 |
| Opus 5 | $0.00038 | $0.00308 |
| Sonnet 5 | $0.00015 | $0.00123 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
wtfp-plan-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 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.
How it starts
The opening of the file, as written. The whole thing — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan a WTF-P Section
Translate the manuscript argument and the author's intent into an executable, verifiable section plan.
Select the action
- Use
discuss-sectionto capture the author's intended reader experience and boundaries. - Use
list-assumptionsto preview the current interpretation without writing files. - Use
plan-sectionto create an evidence-backed writing plan. - Use
plan-revisionto convert review findings into targeted fixes. - Use
insert-sectionorremove-sectionto change outline structure deliberately.
Read references/actions.md for the selected action before changing project state.
Apply the planning contract
- Resolve the section against
project://structure/outlineandproject://sections/{section}; reject ambiguity instead of guessing. - Load
project://manifest,project://state,project://decisions, the outline, prior section summaries,project://sections/{section}/context, andproject://sections/{section}/researchwhen they exist. - For
plan-section, readproject://validations/*and apply the prerequisite selector and decision-fidelity gate in the detailed action reference before any specialist dispatch. - Treat context as author guidance, research as synthesis, source records as identity/provenance, evidence records as claim support, and outline claim IDs as obligations. Preserve those distinctions through planning and checking.
- Honor
project://configgates and its destructive-change safety policy. - Give every plan a concrete objective, declared dependencies, target files, ordered tasks, checkpoints, verification steps, success criteria, and expected outputs.
- Check the plan goal-backward: completing its tasks must be sufficient to satisfy the section goal and assigned claims.
- Iterate on checkable defects; escalate unresolved judgment calls to the author.
- Report the plan path, verification state, open decisions, and next executable action.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 41 lines · 76 tokens per session scan A 160c20748f94
wtfp-plan-section is a skill published in the GitHub repository akougkas/wtf-p (19 stars, last pushed 9d ago), licensed MIT. It adds 76 tokens to every session and 616 once invoked, about $0.0004 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 skills, from other repositories
oh-my-opencode-slim
Configure and improve oh-my-opencode-slim for the current user. Use when users want to tune agents, models, prompts, custom agents, skills, MCPs, presets, or plugin behavior. Also use when recurring workflow friction suggests a safe config or prompt improvement.
clonedeps
Clone important project dependency source code into an ignored local workspace so OpenCode can inspect library internals. Use when the user asks to clone dependencies, inspect dependency/source internals, understand SDK/framework behavior from source, debug library implementation details, or make core dependency repos…
codemap
Generate comprehensive hierarchical codemaps for UNFAMILIAR repositories. Expensive operation - only use when explicitly asked for codebase documentation or initial repository mapping.
deepwork
High-cost orchestrator workflow for large, high-risk, multi-phase coding efforts with meaningful dependencies and review gates. Do not activate for routine multi-file changes.
worktrees
Manage Git worktrees as OMO safe isolated coding lanes for complex, risky, or parallel work.
simplify
Simplifies code for clarity without changing behavior. Use for readability, maintainability, and complexity reduction after behavior is understood.