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.
git clone --depth 1 https://github.com/unclecode/claude-code-toolsWrote 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.
[](https://agentmods.dev/commands/unclecode/claude-code-tools/pp-remove)<a href="https://agentmods.dev/commands/unclecode/claude-code-tools/pp-remove"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-remove/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.
<a href="https://agentmods.dev/commands/unclecode/claude-code-tools/pp-remove"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-remove.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00000 | $0.00582 |
| Opus 5.5 | $0.00000 | $0.00233 |
| Sonnet 5.5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
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 1mo 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.
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
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.
- 1mo ago First seen · 123 lines · 0 tokens per session scan A 2704bdf82da6
pp-remove is a command published in the GitHub repository unclecode/claude-code-tools (4 stars, last pushed 10mo 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.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.