map-project

map-project is a command for Claude Code from akougkas/wtf-p. It costs 15 tokens per session (811 once invoked), scanned A, original, MIT.

A command that indexes an existing research project by recording its drafts, data, figures, references, and supporting evidence in portable project records.

In plain words
What is it for?
Use it when bringing an existing paper project under structured management or updating its inventory of sources and evidence.
Why use it?
It makes an existing collection of research files easier to track without reinitializing the project or losing links between materials.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the wtfp plugin — 36 commands, 3 hooks shipped together

Good fit Use it when bringing an existing paper project under structured management or updating its inventory of sources and evidence.

Compare 6 commands from other repositories ↓
Install

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.

Claude Code
/plugin marketplace add akougkas/wtf-p
Claude Code
/plugin install wtfp

Made for: Claude Code.

Or install wtfp, the plugin that ships this one along with the rest of its 36 commands, 3 hooks.

Wrote 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.

agentmods badge for map-project

README.md
[![agentmods](https://agentmods.dev/badge/commands/akougkas/wtf-p/map-project/github.svg)](https://agentmods.dev/commands/akougkas/wtf-p/map-project)
Your own site
<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.

agentmods 80×15 button for map-project

Your own site · 80×15
<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>
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 811 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 29d ago against content hash b273a4906481, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

vendors/claude/commands/map-project.md · 63 lines

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

  1. Read the current manifest and state, then scan only the authorized project boundary and do not follow escaping symlinks.
  2. Inventory manuscript, notes, bibliography, datasets, figures, tables, and prior drafts with provenance and verification depth.
  3. 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.
  4. 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.
  5. Validate and read back the complete source/evidence and manifest changes before transitioning state to mapped. Retain active checkpoints.

Read the full file on GitHub · 63 lines

Changes

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.

  1. 29d ago Changed b273a4906481
  2. 1mo ago First seen · 63 lines · 15 tokens per session scan A 65a7305382d3

Subscribe to this mod's changes

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.