Borrowing it
Nothing to install: this file belongs to TheSethRose/Copilot-Skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/TheSethRose/Copilot-Skills/main/.github/instructions/cleanup.instructions.mdgit clone --depth 1 https://github.com/TheSethRose/Copilot-SkillsWrote 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/instructions/thesethrose/copilot-skills/cleanup)<a href="https://agentmods.dev/instructions/thesethrose/copilot-skills/cleanup"><img src="https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/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.
<a href="https://agentmods.dev/instructions/thesethrose/copilot-skills/cleanup"><img src="https://agentmods.dev/badge/instructions/thesethrose/copilot-skills/cleanup.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.01058 | $0.01058 |
| Opus 5.5 | $0.00423 | $0.00423 |
| Sonnet 5.5 | $0.00212 | $0.00212 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade C, and why
Copilot-Skills cleanup.instructions.md 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.
rm -rf node_modules/ How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cleanup Operations - Automatic Context Instructions
Related Prompt: /cleanup
Triggers: cleanup, remove, delete, unused, stale, orphan, tidy, clean up
Context: Cleanup and Maintenance Operations
When working with files that match cleanup patterns or when user queries contain cleanup keywords, this context is automatically activated.
Default Behaviors
When user mentions "cleanup" or "unused"
- Suggest
/cleanupskill prompt for guided cleanup workflow - Analyze project for common cleanup targets
- Respect
.gitignorepatterns (never delete ignored files without confirmation) - Create safety checkpoints before destructive operations
When user mentions "dependencies" or "node_modules"
- Check for unused dependencies in package.json, requirements.txt, etc.
- Suggest removal of unused packages
- Warn about breaking changes before removal
- Update lockfiles after changes
When user mentions "cache" or "build artifacts"
- Identify safe-to-delete cache directories
- Preserve development environment configurations
- Keep
.gitignorepatterns up to date
Quality Guidelines
✅ Do
- Always ask for confirmation before deleting files
- Show what will be deleted before executing
- Use dry-run flags when available
- Backup important files before cleanup
- Update
.gitignoreafter cleanup - Clean incrementally (one type at a time)
❌ Don't
- Delete files matching
.gitignorewithout explicit confirmation - Remove dependencies without checking usage
- Clean production builds without backup
- Delete configuration files
- Remove version control history
- Clean without showing file list first
Common Cleanup Targets
Safe to Remove (Usually)
# Build artifacts
dist/
build/
*.egg-info/
target/
# Cache directories
__pycache__/
.pytest_cache/
.mypy_cache/
.ruff_cache/
node_modules/.cache/
.next/
.nuxt/
# Log files
*.log
npm-debug.log*
yarn-debug.log*
yarn-error.log*
# Temporary files
*.tmp
*.temp
.DS_Store
Thumbs.db
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 · 210 lines · 1,058 tokens per session scan C f17cd48d3857
Copilot-Skills cleanup.instructions.md is an instructions file published in the GitHub repository TheSethRose/Copilot-Skills (3 stars, last pushed 10mo ago), licensed MIT. It adds 1,058 tokens to every session, about $0.0042 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.