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-create-poster)<a href="https://agentmods.dev/commands/akougkas/wtf-p/wtfp-create-poster"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-create-poster/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-create-poster"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-create-poster.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.00771 |
| Opus 5.5 | $0.00009 | $0.00308 |
| Sonnet 5.5 | $0.00004 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
wtfp:create-poster 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 1mo 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 — 60 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create a research poster
@${PLUGIN_ROOT}/project/README.md @${PLUGIN_ROOT}/skills/wtfp-deliver-research/SKILL.md @${PLUGIN_ROOT}/skills/wtfp-deliver-research/references/actions.md
Record contract
Read: project://manifest, project://structure/outline, project://paper/{artifact}.
Produce: project://deliverables/poster/{artifact} (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
- Confirm audience, dimensions, format, emphasis, and the exact author, affiliation, contact, funding, and venue metadata, following the confirmation list in
${PLUGIN_ROOT}/templates/poster.md. Never invent missing metadata; leave the visible placeholder the template names. 1a. Start from the layout, panel structure, and word budgets in${PLUGIN_ROOT}/templates/poster.md. Delete any panel the manuscript does not support rather than filling it. - Run the evidence gate in
${PLUGIN_ROOT}/templates/poster.md: build the claim ledger and refuse every statement, comparison, or figure without a cited source record, manuscript passage, or named project file. Derive each diagram from named source files or documents and state their paths beneath it. - Write the poster as laid-out source (the template's HTML skeleton, or the venue's mandated template carrying the same grid and type scale) plus its assets and claim ledger under the declared deliverable URI, without changing project records except through a separately declared action. This action produces poster source, not a rendered image or PDF: WTF-P declares no rendering effect and runs no renderer. If the author asks for a rendered artifact, return a labeled handoff naming the exact command they can run in their own toolchain.
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.
- 1mo ago Changed dfaf889ec841
- 1mo ago Changed · +42 lines 371b1908544a
- 1mo ago First seen · 18 lines · 22 tokens per session scan A de30da033058
wtfp:create-poster is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 19d ago), licensed MIT. It adds 22 tokens to every session and 771 once invoked, about $0.0001 per session on Opus 5.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
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.