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.
npx agentmods add commands/unclecode/claude-code-tools/pp-migrate-v2git clone --depth 1 https://github.com/unclecode/claude-code-toolsWhat 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 | $0.00000 | $0.01801 |
| Opus 5 | $0.00000 | $0.00901 |
| Sonnet 5 | $0.00000 | $0.00360 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
pp-migrate-v2 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 yesterday.
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 — 263 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrate PP v1.0 to v1.1+ Structure
TEMPORARY COMMAND: Upgrades old Project Planning structure (v1.0.0) to new structure (v1.1.0+).
Arguments
None
Purpose
Migrate existing PP projects from old structure (with root STATUS.md, CODEBASE.md, CHANGELOG.md) to new simplified structure (with combined INDEX.md).
Use this if you have projects using the old PP structure that need upgrading.
What Changes
Old Structure (v1.0.0):
.context/project/
├── INDEX.md (old format)
├── STATUS.md ← will be archived
├── CODEBASE.md ← will be archived
├── CHANGELOG.md ← will be archived
├── WORKFLOW.md (old)
└── subproject/
New Structure (v1.1.0+):
.context/project/
├── INDEX.md ← NEW (combines INDEX + STATUS + high-level TODOs)
├── WORKFLOW.md ← UPDATED
├── PRINCIPLES.md
├── LESSONS.md
└── subproject/ ← UNCHANGED
Execution Instructions
Step 1: Detect Old Structure
Check if this is an old PP structure:
ls .context/project/STATUS.md
If STATUS.md doesn't exist:
- Inform user: "Project already using new structure or not initialized. Nothing to migrate."
- Exit
If STATUS.md exists:
- Proceed to Step 2
Step 2: Read Old Files
Read and extract data from old files:
From STATUS.md:
- Active subproject (section: "## Active Subproject")
- Subproject summary table (section: "## Subproject Summary")
- Overall progress (if any)
- Cross-project dependencies (if any)
- Recent decisions (if any)
From INDEX.md (old):
- Project name
- Project description
- Created date
- Subprojects table
- Environment info
From CODEBASE.md:
- Check if it had any important root-level file listings
- (Usually empty or minimal in old structure)
From CHANGELOG.md:
- Check if it had any cross-project entries
- (Usually empty or minimal in old structure)
Step 3: Create New INDEX.md
Generate new INDEX.md using the template from pp-init-assets/templates/root/INDEX.md:
Populate with extracted data:
{{PROJECT_NAME}}- from old INDEX.md{{PROJECT_DESCRIPTION}}- from old INDEX.md{{DATE}}- original created date from old INDEX.md{{ACTIVE_SUBPROJECT}}- from old STATUS.md{{SUBPROJECT_TABLE}}- from old INDEX.md{{SUBPROJECT_STATUS_TABLE}}- from old STATUS.md{{ENVIRONMENT}}- from old INDEX.md{{TODO_ITEM_1}},{{TODO_ITEM_2}},{{TODO_ITEM_3}}- set to "TBD" or extract from context
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.
- yesterday First seen · 263 lines · 0 tokens per session scan A 0df460e7e73e
pp-migrate-v2 is a command published in the GitHub repository unclecode/claude-code-tools (4 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,801 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.