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-clean)<a href="https://agentmods.dev/commands/unclecode/claude-code-tools/pp-clean"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-clean.svg" alt="Measured on agentmods" 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.01076 |
| Opus 5 | $0.00000 | $0.00538 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00108 |
Grade A, and why
pp-clean 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 6d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clean Project Files
Clean up temporary files and archive useful markdown.
Arguments
$ARGUMENTS
Purpose
After tasks/updates, clean up the project:
- Delete truly temporary files (test outputs, scratch, debug logs)
- Archive potentially useful markdown (drafts, notes, old versions)
- Keep project directory clean while preserving history
Execution Instructions
Step 1: Scan for Files to Clean
Look in project root and common locations for:
Temporary files (to DELETE):
*_test.md,test_*.mdscratch*.md,temp*.md,tmp*.mddebug*.md,*_debug.md*.log(unless in logs/ folder)output*.md,*_output.md- Files with
DELETEorTEMPin name
Potentially useful markdown (to ARCHIVE):
draft_*.md,*_draft.mdnotes_*.md,*_notes.mdresearch_*.mdold_*.md,*_old.md,*_backup.mdv1_*.md,*_v1.md(old versions)- Any
.mdfile in root that's not part of standard structure - User-created markdown during session
Step 2: Parse Optional Query
If query provided, focus on:
- Specific pattern:
/pp-clean test files - Specific folder:
/pp-clean webhook/ - Specific action:
/pp-clean archive onlyor/pp-clean delete only
Step 3: Show Preview
## Cleanup Preview
### To DELETE (temporary files)
- scratch_booking.md
- test_output.md
- debug_log.md
### To ARCHIVE (move to .context/project/archive/)
- draft_system_prompt.md
- research_notes.md
- old_booking_flow.md
### No Action
- (files that look fine)
---
Proceed with cleanup? (yes/no/edit)
If user says "edit", allow them to:
- Move items between delete/archive
- Skip specific files
- Add files to clean
Step 4: Execute Cleanup
Delete temporary files:
rm {temp_files}
Archive useful markdown:
# Create dated archive subfolder if multiple files
mkdir -p .context/project/archive/cleanup_{date}
mv {markdown_files} .context/project/archive/cleanup_{date}/
Or if single file:
mv {file} .context/project/archive/{file}
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.
- 6d ago First seen · 195 lines · 0 tokens per session scan A 2dc9e7fd6cfc
pp-clean 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,076 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
cancel-ralph
Cancel active Ralph Loop.
obsidian-recap
Summarize a time period from the vault - today, week, or month.
setup-pm-skills
Onboard a new user — find out what they do, recommend the right bundles & top skills, and set up a project CONTEXT.md so every skill is tailored to them.
statusbar-style
Switch the status-bar style (classic / capsule / hairline).
engage.actions
Execute Phase 7 - Actions on Objectives and Goal Achievement.
superpowers-execute
Execute the current GSD phase plan with Superpowers instead of gsd-execute-phase.