A workspace cleanup helper for removing selected development files, such as build output, installed dependencies, caches, temporary task files, or unused Docker data.

Use it to inspect or clean build artifacts, dependency folders, caches, Docker data, obsolete task files, or to perform a full dependency reinstall.

Generated files and caches can consume disk space or cause confusing stale-state problems. Choosing a cleanup scope helps remove only the category you intend to clear.

cleanup — Skill for Claude Code by brain-bootstrap

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.

Any agent

npx skills add brain-bootstrap/claude-code-brain-bootstrap --skill cleanup

Clone the repo

git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrap

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/cleanup/github.svg)](https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/cleanup)

Your own site

<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/cleanup"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/cleanup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/cleanup"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 37 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 518 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 1 finding. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00037	$0.00518
Opus 5.5	$0.00015	$0.00207
Sonnet 5.5	$0.00007	$0.00104
Haiku 4.5	$0.00004	$0.00052

Measured 1mo ago against content hash e9de30bf9fa6, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

cleanup scanned grade C with 1 finding 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- NEVER run `rm -rf /`

.claude/skills/cleanup/SKILL.md · 49 lines

What it actually says

Cleanup Skill

Clean up workspace artifacts based on the requested scope.

Usage

/cleanup              # Default: show what can be cleaned
/cleanup build        # Remove build artifacts
/cleanup deps         # Remove dependency directories (node_modules, venv, etc.)
/cleanup all          # Full clean: deps + build artifacts
/cleanup cache        # Clear build tool caches
/cleanup docker       # docker system prune -f (no named volumes removed)
/cleanup tasks        # Remove obsolete task files (lessons.md is NEVER deleted)
/cleanup reinstall    # Full reinstall: clean deps → install

Instructions

Determine action from $ARGUMENTS:

Argument	Action
`build` or `dist`	Remove all build artifacts (`dist/`, `build/`, `.next/`, `target/`)
`deps`	Remove dependency directories (`node_modules/`, `venv/`, `.venv/`, `target/`)
`all`	Full clean: deps + build artifacts, then reinstall
`cache`	Clear build tool caches (`.turbo/`, `.cache/`, `__pycache__/`, `.mypy_cache/`)
`docker`	`docker system prune -f` (does NOT remove named volumes)
`tasks`	Clean obsolete task files (see rules below)
`reinstall`	Full reinstall: clean deps → install

Tasks file cleanup rules:

NEVER delete claude/tasks/lessons.md (accumulated wisdom)
NEVER delete claude/tasks/CLAUDE_ERRORS.md (bug history)
claude/tasks/todo.md can be archived if no active task
claude/tasks/mr-description-*.md can be deleted after MR is merged
claude/tasks/ticket-*.md can be deleted after ticket is created

Safety rules:

NEVER run rm -rf /
NEVER delete .env or .env.* files
For all: confirm before deleting dependencies if package.json/pyproject.toml shows install script hooks
For docker: confirm before running prune in production-adjacent environments

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.

1mo ago First seen · 49 lines · 37 tokens per session scan C e9de30bf9fa6

Subscribe to this mod's changes

cleanup is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 37 tokens to every session and 518 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Claude Code DevOps and cloud claude-config claude-context

implement

TRIGGER when: user asks to implement, fix, build, or work on something — whether from a docs/feat/wip plan OR a standalone task (bug fix, GitHub issue, one-off change). Examples: "work on task 1", "fix this bug", "implement feature X from the issue". Provides structured execution with profile detection, dependency…

serpro69/claude-toolbox · 81 tokens

review-spec

Use after implementing tasks or mid-feature to verify code matches design docs and ensure they are in sync. Detects spec deviations, missing implementations, doc inconsistencies, and outdated docs in design and implementation documentation.

serpro69/claude-toolbox · 44 tokens

chain-of-verification

Apply Chain-of-Verification (CoVe) prompting to improve response accuracy through self-verification. Use when complex questions require fact-checking, technical accuracy, or multi-step reasoning.

serpro69/claude-toolbox · 41 tokens

review-design

Review design, implementation, and task documents produced by design. Evaluates document quality, internal consistency, and technical soundness. Use after design completes and before starting implement.

serpro69/claude-toolbox · 37 tokens

review-architecture

Review a written architecture artifact — an ADR (docs/adr/), a broader architecture doc, the architecture section of a design doc, or a domain-reference kit (glossary + traps pages, reviewed as one composite artifact) — against the system it claims to describe. Verifies the EXISTENCE and TOPOLOGY of declared…

serpro69/claude-toolbox · 183 tokens

model

Produce or update a domain-reference kit — the durable glossary + divergences/traps pages for a bounded context. Use for domain modelling, information architecture, building a domain glossary or domain model, mapping domain concepts to code (bindings), or surfacing the decidable questions stakeholders must close…

serpro69/claude-toolbox · 129 tokens

cleanup