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-map-project)<a href="https://agentmods.dev/commands/akougkas/wtf-p/wtfp-map-project"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-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/wtfp-map-project"><img src="https://agentmods.dev/badge/commands/akougkas/wtf-p/wtfp-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.00021 | $0.00781 |
| Opus 5.5 | $0.00008 | $0.00312 |
| Sonnet 5.5 | $0.00004 | $0.00156 |
| Haiku 4.5 | $0.00002 | $0.00078 |
Grade A, and why
wtfp: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 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.
This is a copy
88% identical to wtfp:add-todo — 32 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.
Map an existing project
@${PLUGIN_ROOT}/project/README.md @${PLUGIN_ROOT}/skills/wtfp-start-project/SKILL.md @${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.
- 1mo ago Changed 300ae69fe195
- 1mo ago Changed · +2 lines 8d1683ed6006
- 1mo ago First seen · 62 lines · 21 tokens per session scan A fd835b8e73cd
wtfp:map-project is a command published in the GitHub repository akougkas/wtf-p (20 stars, last pushed 19d ago), licensed MIT. It adds 21 tokens to every session and 781 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to wtfp:add-todo, differing in 32 lines, and is treated as a copy.
Other commands, from other repositories
status
Display project status, active tracks, and next actions.
cs-internal-comms
Internal-only change-management comms using ADKAR (Prosci) + Kotter's 8-step. NOT marketing (external) and NOT executive narrative strategy. Direct invocation of the internal-comms skill.
cs-process-map
Map an internal business process (BPMN-style swim lanes), measure cycle time, and detect bottlenecks where work spends most of its time waiting. Direct invocation of the process-mapper skill.
continue
Detects current wave progress for a feature and resumes at the next step. Scans docs/feature/ for artifacts.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.