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.
npx agentmods add commands/cwakim/claude-plugins/cleanupgit clone --depth 1 https://github.com/cwakim/claude-pluginsWhat 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.00028 | $0.01076 |
| Opus 5 | $0.00014 | $0.00538 |
| Sonnet 5 | $0.00006 | $0.00215 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
cleanup 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 2d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch Cleanup
Delete the branches that are fully merged into a base branch, both locally and
on the remote, then report what was removed and what was kept. Long-lived branches
are protected, the branch you are currently on is never touched, and unmerged work
is left strictly alone (only safe git branch -d, never force-delete -D).
This is housekeeping after merges land: it removes the stale feat/*, fix/*, and
similar branches whose commits already live in the base, so git branch stops being
a junkyard. It does not decide what to merge and it never deletes anything that
is not already merged.
Arguments
$ARGUMENTS is optional and freeform:
- A branch name (e.g.
develop,main) sets the base to compare against. If omitted, use the repository's default branch (see step 1). --dry-runlists what would be deleted and stops, without deleting or asking.--local-onlyskips remote deletion entirely (never touchesorigin).
Examples: /cleanup, /cleanup develop, /cleanup main --dry-run,
/cleanup --local-only.
Protected branches
Never delete, regardless of merge status:
- The base branch itself.
- The current branch (the one
HEADpoints at). - A default keep-list of common long-lived branches:
main,master,develop,development,preview,staging,production,release.
If the user has named other long-lived branches in this repo's CLAUDE.md or in the
conversation, treat those as protected too.
Steps
-
Determine the base branch. If
$ARGUMENTSnames one, use it. Otherwise detect the repo default:git remote show origin 2>/dev/null | sed -n 's/.*HEAD branch: //p'If that yields nothing (no remote), fall back to
mainif it exists, elsemaster. Confirm the chosen base out loud before deleting anything. -
Refresh the branch list so merged-state and remote-tracking refs are current:
git fetch --prune origin(Skip the fetch if there is no
originremote.)
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.
- 2d ago First seen · 94 lines · 28 tokens per session scan A 0bf15ab78659
cleanup is a command published in the GitHub repository cwakim/claude-plugins (2 stars, last pushed 12d ago), licensed MIT. It adds 28 tokens to every session and 1,076 once invoked, about $0.0001 per session on Opus 5. 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.