pp-add

A command for adding a new subproject, meaning a separately organized part of a larger project, to a repository's project structure.

In plain words
What is it for?
It helps create a named subproject with documentation, planning folders, an optional scope, and links to its dependencies.
Why use it?
It removes the need to create the expected folders and planning files by hand and helps keep new subprojects consistent.

Command

Install

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.

agentmods
npx agentmods add commands/unclecode/claude-code-tools/pp-add
Clone the repo
git clone --depth 1 https://github.com/unclecode/claude-code-tools
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 697 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00697
Opus 5 $0.00000 $0.00349
Sonnet 5 $0.00000 $0.00139
Haiku 4.5 $0.00000 $0.00070

Measured yesterday against content hash 253c819102e9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

pp-add 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.

plugins/unclecode-cc-toolkit/commands/pp-add.md · 121 lines

How it starts

The opening of the file, as written. The whole thing — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add New Subproject

Create a new subproject in the project structure.

Arguments

$ARGUMENTS

Purpose

Add a new subproject with full file structure. Query should contain:

  • Subproject name (folder name)
  • Description/purpose
  • Optionally: initial scope, dependencies

Execution Instructions

Step 1: Parse Query

Extract from query:

  • name: Folder name (lowercase, no spaces)
  • title: Human-readable title
  • description: What this subproject does
  • dependencies: Relationships to other subprojects

If query is empty or missing info, ask:

  1. "Subproject folder name (e.g., 'api', 'frontend'):"
  2. "Title (e.g., 'REST API Backend'):"
  3. "Brief description:"
  4. "Dependencies on other subprojects? (optional)"

Step 2: Create Directory Structure

mkdir -p .context/project/{name}/prds .context/project/{name}/docs .context/project/{name}/archive

Step 3: Copy and Process Templates

Copy subproject templates from ~/.claude/commands/pp-init-assets/templates/subproject/:

# Copy all subproject templates
cp ~/.claude/commands/pp-init-assets/templates/subproject/*.md .context/project/{name}/

Then process placeholders:

  • {{SUBPROJECT_NAME}} → name
  • {{SUBPROJECT_TITLE}} → title
  • {{SUBPROJECT_DESCRIPTION}} → description
  • {{DATE}} → current date
  • {{SUBPROJECT_STATUS}} → "Not Started"
  • Other placeholders → "TBD" or empty

Step 4: Update Root Files

INDEX.md: Add to subproject table

| {name}/ | Planned | {description} |

STATUS.md: Add to subproject summary table

| {name}/ | - | Not Started |

CODEBASE.md: Add to subproject refs

- `{name}/CODEBASE.md` - {title} files

CHANGELOG.md: Add entry

## {DATE} | Added Subproject: {name}

**Changes**:
- Created {name}/ subproject structure

**Context**:
- {description}

Step 5: Confirm Creation

## Created Subproject: {name}/

**Title**: {title}
**Description**: {description}

**Files created**:
- {name}/INDEX.md
- {name}/STATUS.md
- {name}/TODO.md
- {name}/CHANGELOG.md
- {name}/PRINCIPLES.md
- {name}/CODEBASE.md
- {name}/LESSONS.md

**Updated**:
- Root INDEX.md
- Root STATUS.md
- Root CODEBASE.md
- Root CHANGELOG.md

To start working on this subproject, update STATUS.md to set it as active.

Read the full file on GitHub · 121 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. yesterday First seen · 121 lines · 0 tokens per session scan A 253c819102e9

Subscribe to this mod's changes

pp-add 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 697 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.