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-initgit 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.01336 |
| Opus 5 | $0.00000 | $0.00668 |
| Sonnet 5 | $0.00000 | $0.00267 |
| Haiku 4.5 | $0.00000 | $0.00134 |
Grade A, and why
pp-init 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Initialize Project Management Structure
Generate a multi-subproject management structure in .context/project/.
Note: For small projects needing only one subproject, use the name "main" as the default.
Arguments
$ARGUMENTS
Assets Location
Template files are in ~/.claude/commands/pp-init-assets/templates/:
root/- Root level templates (WORKFLOW.md, PRINCIPLES.md, etc.)subproject/- Subproject templates
Execution Instructions
Step 1: Parse Arguments
Check for mode:
--quietor-q→ Quiet mode- Contains text (not flags) → Description mode
- Empty → Interactive mode
Step 2: Create Directory Structure
# Create root directories
mkdir -p .context/project/prds .context/project/docs .context/project/archive
# Create subproject directories (for each subproject)
mkdir -p .context/project/{subproject}/prds
mkdir -p .context/project/{subproject}/docs
mkdir -p .context/project/{subproject}/archive
mkdir -p .context/project/{subproject}/history
Note: The history/ directory stores ultra-compact session summaries created by /pp-checkpoint.
Step 3: Copy Fixed Templates
These files are copied as-is (no placeholders to fill):
# Copy WORKFLOW.md, PRINCIPLES.md, and LESSONS.md (fully populated)
cp ~/.claude/commands/pp-init-assets/templates/root/WORKFLOW.md .context/project/
cp ~/.claude/commands/pp-init-assets/templates/root/PRINCIPLES.md .context/project/
cp ~/.claude/commands/pp-init-assets/templates/root/LESSONS.md .context/project/
Note: Root level only has WORKFLOW, PRINCIPLES, LESSONS. All tracking files (STATUS, TODO, CHANGELOG, CODEBASE) live in subprojects.
Step 4: Process Template Files
For files with {{PLACEHOLDER}} markers:
- Read template from assets
- Replace placeholders with collected data
- Write to destination
Root templates to process:
- INDEX.md (combines project overview + active subproject + high-level TODOs + status summary)
Subproject templates to process (for each subproject):
- INDEX.md
- STATUS.md
- TODO.md
- CHANGELOG.md
- PRINCIPLES.md (optional - only if different from root)
- CODEBASE.md
- LESSONS.md
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 · 165 lines · 0 tokens per session scan A d52439a5e9ac
pp-init 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,336 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.