A command for safely removing a subproject from a project's tracked structure by archiving it and updating references.

Use it to remove a subproject, check whether it is active, archive its folder, and update project documentation after confirmation.

It reduces the risk of losing project history and helps keep overview files consistent after removal.

pp-remove — Command by unclecode

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-remove

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

Model	Per session	Once invoked
Fable 5	$0.00000	$0.00582
Opus 5	$0.00000	$0.00291
Sonnet 5	$0.00000	$0.00116
Haiku 4.5	$0.00000	$0.00058

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

Security

Grade A, and why

pp-remove 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-remove.md · 123 lines

How it starts

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

Remove Subproject

Remove a subproject from the project structure.

Arguments

$ARGUMENTS

Purpose

Safely remove a subproject. This will:

Archive the subproject folder (not delete)
Update root files to remove references
Log the removal

Execution Instructions

Step 1: Parse Query

Extract subproject name from query.

If empty, list available subprojects and ask which to remove.

Step 2: Verify Subproject Exists

ls .context/project/{name}/INDEX.md

If not found, show error: "Subproject '{name}' not found."

Step 3: Check if Active

Read .context/project/STATUS.md to check if this is the active subproject.

If active, ask: "This is the active subproject. Which subproject should become active instead?"

Step 4: Confirm Removal

Show warning:

## Removing Subproject: {name}/

This will:
- Archive {name}/ to archive/{name}_{date}/
- Remove from INDEX.md subproject table
- Remove from STATUS.md summary
- Remove from CODEBASE.md refs
- Add removal entry to CHANGELOG.md

Files will NOT be deleted, just archived.

Proceed? (yes/no)

Wait for confirmation.

Step 5: Archive Subproject

mv .context/project/{name} .context/project/archive/{name}_{date}

Step 6: Update Root Files

INDEX.md: Remove from subproject table

STATUS.md:

Remove from subproject summary table
If was active, update active subproject

CODEBASE.md: Remove from subproject refs

CHANGELOG.md: Add entry

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

**Changes**:
- Archived {name}/ to archive/{name}_{date}/
- Removed from project structure

**Context**:
- {reason if provided}
- Files preserved in archive

Step 7: Confirm Removal

## Removed Subproject: {name}/

**Archived to**: archive/{name}_{date}/
**Active subproject**: {new_active}

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

To restore, move from archive back to project root.

Query Examples

# With name
/pp-remove old-api

# With reason
/pp-remove old-api - replaced by new api design

# Interactive (will list and ask)
/pp-remove

Read the full file on GitHub · 123 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.

yesterday First seen · 123 lines · 0 tokens per session scan A 2704bdf82da6

Subscribe to this mod's changes

pp-remove 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 582 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.

Writing and docs

pp-remove