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/map-project)<a href="https://agentmods.dev/commands/akougkas/wtf-p/map-project"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/map-project/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/map-project"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/map-project.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.00015 | $0.00811 |
| Opus 5.5 | $0.00006 | $0.00324 |
| Sonnet 5.5 | $0.00003 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
map-project 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.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map an existing project
@${CLAUDE_PLUGIN_ROOT}/project/README.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-start-project/SKILL.md @${CLAUDE_PLUGIN_ROOT}/skills/wtfp-start-project/references/actions.md
Record contract
Read: project://manifest, project://state, project://materials/{artifact}, project://paper/{artifact}, project://sources/{source}, project://evidence/{evidence}.
Produce: project://sources/{source} (create), project://evidence/{evidence} (create), project://state (update), project://sources/{source} (update), project://evidence/{evidence} (update), project://manifest (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
- Read the current manifest and state, then scan only the authorized project boundary and do not follow escaping symlinks.
- Inventory manuscript, notes, bibliography, datasets, figures, tables, and prior drafts with provenance and verification depth.
- Read existing source and evidence records before merging by stable identity. Create missing records; update existing records only after inspecting them. Preserve IDs, curated annotations and stronger verification depth; report duplicate identifiers and citation-key collisions rather than overwriting them.
- Merge selected material and manuscript URIs into the manifest artifact indexes without removing existing entries or changing authored files. Preserve all unrelated manifest fields and set updated_at to the actual update time only when the index changes.
- Validate and read back the complete source/evidence and manifest changes before transitioning state to mapped. Retain active checkpoints.
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 b273a4906481
- 1mo ago First seen · 63 lines · 15 tokens per session scan A 65a7305382d3
map-project is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 11d ago), licensed MIT. It adds 15 tokens to every session and 811 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-09-15.
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.