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/discuss-section)<a href="https://agentmods.dev/commands/akougkas/wtf-p/discuss-section"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/discuss-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/commands/akougkas/wtf-p/discuss-section"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/discuss-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.00017 | $0.00765 |
| Opus 5.5 | $0.00007 | $0.00306 |
| Sonnet 5.5 | $0.00003 | $0.00153 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
discuss-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 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
80% identical to add-todo — 31 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Discuss a section
@${CLAUDE_PLUGIN_ROOT}/project/README.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-plan-section/SKILL.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-plan-section/references/actions.md
Record contract
Read: project://manifest, project://decisions, project://structure/outline, project://sections/{section}, project://sections/{section}/context, project://sections/{section}/summary.
Produce: project://sections/{section}/context (create), project://sections/{section}/context (update), project://checkpoints/{checkpoint} (create), project://sections/{section} (update), project://decisions (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
- Resolve one section ID from the outline and read its prior context, summary, and decisions before proposing updates; reject ambiguity.
- Elicit the section purpose, boundaries, claims, examples, evidence needs, exclusions, and discretionary choices.
- Store prose guidance as the section context artifact, decisions as decision records, and unresolved blocking choices as checkpoints; link artifacts from the section record.
Safety and completion
Do not initialize a repository or run branch, stage, commit, merge, push, or publish operations. If requested, return a clearly labeled optional handoff for a separately authorized action.
Report the logical resources read, created, updated, archived, or deleted; the gates crossed; validation results; unresolved checkpoints; and the safest next action. Never claim a mutation that was not verified.
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 fe2dd8114c4c
- 1mo ago First seen · 64 lines · 17 tokens per session scan A 233cc0a527bb
discuss-section is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 11d ago), licensed MIT. It adds 17 tokens to every session and 765 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 80% identical to add-todo, differing in 31 lines, and is treated as a copy.
Other commands, from other repositories
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.
openehr-explain
One-stop router that explains or looks up any openEHR thing — auto-detects an archetype, a template, an RM/AM/BASE type, an RM structural concept, an ADL idiom, an AQL query or keyword, or a terminology code (replaces /archetype-explain, /template-explain, /type-spec, /rm-structure, /adl-idiom, /terminology).
gpd:write-paper
Structure and write a physics paper from project research results or a bounded external-authoring intake.
gpd:derive-equation
Perform a rigorous physics derivation with systematic verification at each step.
gpd:limiting-cases
Systematically identify and verify all relevant limiting cases for a result or phase.