pp-clean

pp-clean is a command for Claude Code from unclecode/claude-code-tools. It costs 0 tokens per session (1,076 once invoked), scanned A, original, MIT.

A cleanup command for project files that deletes files marked as temporary and moves potentially useful Markdown notes into an archive. Markdown is a plain-text document format commonly used for notes and documentation.

In plain words
What is it for?
Use it after development tasks to clean temporary outputs, debug logs, and disposable notes, or to archive selected files and folders.
Why use it?
It removes scratch files and old clutter while keeping drafts, research, notes, and previous versions available for later reference.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: mentions CLAUDE.md.

Part of the unclecode-cc-toolkit plugin — 2 skills, 15 commands shipped together

Good fit Use it after development tasks to clean temporary outputs, debug logs, and…

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/unclecode/claude-code-tools/pp-clean
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.

Clone the repo
git clone --depth 1 https://github.com/unclecode/claude-code-tools

Made for: Claude Code.

Or install unclecode-cc-toolkit, the plugin that ships this one along with the rest of its 2 skills, 15 commands.

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

agentmods badge for pp-clean

README.md
[![agentmods](https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-clean.svg)](https://agentmods.dev/commands/unclecode/claude-code-tools/pp-clean)
Your own site
<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>
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 1,076 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.01076
Opus 5 $0.00000 $0.00538
Sonnet 5 $0.00000 $0.00215
Haiku 4.5 $0.00000 $0.00108

Measured 6d ago against content hash 2dc9e7fd6cfc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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.

plugins/unclecode-cc-toolkit/commands/pp-clean.md · 195 lines

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:

  1. Delete truly temporary files (test outputs, scratch, debug logs)
  2. Archive potentially useful markdown (drafts, notes, old versions)
  3. 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_*.md
  • scratch*.md, temp*.md, tmp*.md
  • debug*.md, *_debug.md
  • *.log (unless in logs/ folder)
  • output*.md, *_output.md
  • Files with DELETE or TEMP in name

Potentially useful markdown (to ARCHIVE):

  • draft_*.md, *_draft.md
  • notes_*.md, *_notes.md
  • research_*.md
  • old_*.md, *_old.md, *_backup.md
  • v1_*.md, *_v1.md (old versions)
  • Any .md file 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 only or /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}

Read the full file on GitHub · 195 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. 6d ago First seen · 195 lines · 0 tokens per session scan A 2dc9e7fd6cfc

Subscribe to this mod's changes

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.