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 skills/edison-watch/custom-mcps/cleanupnpx skills add Edison-Watch/Custom-MCPs --skill cleanupgit clone --depth 1 https://github.com/Edison-Watch/Custom-MCPsWrote 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/skills/edison-watch/custom-mcps/cleanup)<a href="https://agentmods.dev/skills/edison-watch/custom-mcps/cleanup"><img src="https://agentmods.dev/badge/skills/edison-watch/custom-mcps/cleanup.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 | $0.00018 | $0.00935 |
| Opus 5 | $0.00009 | $0.00467 |
| Sonnet 5 | $0.00004 | $0.00187 |
| Haiku 4.5 | $0.00002 | $0.00093 |
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 4d 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.
This is a copy
100% identical to cleanup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Cleanup Skill
Automates git branch hygiene after merging or closing PRs. Safely deletes merged branches (and force-deletes closed/abandoned branches), prunes stale remote tracking refs, syncs dependencies, and runs garbage collection.
Workflow
Execute these steps in order:
1. Check current branch
git branch --show-current
Store the result as CURRENT_BRANCH.
2. Guard against main/master
If CURRENT_BRANCH is main or master:
- Report: "Already on main branch. No branch to clean up."
- Skip to step 7 (pull latest) and continue from there.
3. Check for uncommitted changes
git status --porcelain
If output is non-empty:
- Warn the user: "You have uncommitted changes. Please commit or stash them first."
- Stop and do not proceed.
4. Check if branch is merged or closed
First check for merged PRs:
gh pr list --state merged --head CURRENT_BRANCH --json number
If merged, proceed to step 5.
If not merged, check for closed PRs:
gh pr list --state closed --head CURRENT_BRANCH --json number
If closed (result is non-empty):
- Report: "Branch 'CURRENT_BRANCH' has a closed (unmerged) PR. Proceeding with deletion."
- Proceed to step 5 (will use force delete in step 6).
If neither merged nor closed:
- Check if the branch is merged locally:
git branch --merged main | grep -w CURRENT_BRANCH - If not merged anywhere, warn: "Branch 'CURRENT_BRANCH' does not appear to be merged or closed. Use
git branch -Dmanually if you want to force delete." - Stop and do not proceed.
Store whether the branch was MERGED or CLOSED for use in step 6.
5. Switch to main
git checkout main
6. Delete the branch
If branch was MERGED:
git branch -d CURRENT_BRANCH
If branch was CLOSED (PR closed without merging):
git branch -D CURRENT_BRANCH
Report: "Deleted branch CURRENT_BRANCH." (mention if force-deleted due to closed PR)
7. Pull latest
git pull origin main
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.
- 4d ago First seen · 144 lines · 18 tokens per session scan A 780430af12b6
cleanup is a skill published in the GitHub repository Edison-Watch/Custom-MCPs (0 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 935 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cleanup, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…