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/istarwyh/mcpadvisor/cleanupgit clone --depth 1 https://github.com/istarwyh/mcpadvisorWrote 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/commands/istarwyh/mcpadvisor/cleanup)<a href="https://agentmods.dev/commands/istarwyh/mcpadvisor/cleanup"><img src="https://agentmods.dev/badge/commands/istarwyh/mcpadvisor/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.00000 | $0.02896 |
| Opus 5 | $0.00000 | $0.01448 |
| Sonnet 5 | $0.00000 | $0.00579 |
| Haiku 4.5 | $0.00000 | $0.00290 |
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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf dist build .cache coverage How it starts
The opening of the file, as written. The whole thing — 442 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Please clean up the repository by removing stale branches and performing maintenance tasks: $ARGUMENTS.
REPOSITORY MAINTENANCE PRINCIPLES
Core Principles
- Keep It Clean: Regular maintenance prevents technical debt accumulation
- Automate Where Possible: Use scripts and CI/CD for routine tasks
- Document Everything: Maintain clear records of maintenance activities
- Test Before & After: Verify functionality before and after maintenance
- Follow Git Flow: Maintain a clear branching strategy and workflow
Best Practices Timeline
- Daily: Small cleanups during development
- Weekly: Branch pruning and dependency checks
- Monthly: Deep cleaning and optimization
- Quarterly: Major dependency updates and security audits
EXECUTION PLAN
1. Preparation & Safety Measures
-
Create a backup branch before cleanup:
git checkout -b backup-before-cleanup-$(date +%Y%m%d) git checkout main -
Document current state:
# Save current branch list for reference git branch -a > branch-list-before-cleanup.txt # Document current dependencies pnpm list > dependencies-before-cleanup.txt
2. Branch Management
-
Fetch latest updates from remote:
# Fetch all branches and prune references to deleted remote branches git fetch --all --prune -
Switch to main branch and update:
git checkout main git pull origin main -
Clean up local branches that have been merged to main:
# List branches to be deleted first for review echo "Local branches to be deleted:" git branch --merged main | grep -v "^\*\|main\|master\|develop" # Then delete them after confirmation git branch --merged main | grep -v "^\*\|main\|master\|develop" | xargs -n 1 git branch -d -
Find and clean up remote branches that have been merged to main:
# List branches to be deleted first for review echo "Remote branches to be deleted:" git branch -r --merged main | grep -v "^\*\|main\|master\|develop" | sed 's/origin\///' # Then delete them after confirmation git branch -r --merged main | grep -v "^\*\|main\|master\|develop" | sed 's/origin\///' | xargs -I{} git push origin --delete {}
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 · 442 lines · 0 tokens per session scan C 3f3a77411af2
cleanup is a command published in the GitHub repository istarwyh/mcpadvisor (89 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,896 tokens. 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.
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.