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 skills add basher83/lunar-claude --skill branch-cleanupgit clone --depth 1 https://github.com/basher83/lunar-claudeWrote 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/basher83/lunar-claude/branch-cleanup)<a href="https://agentmods.dev/skills/basher83/lunar-claude/branch-cleanup"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/branch-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/skills/basher83/lunar-claude/branch-cleanup"><img src="https://agentmods.dev/badge/skills/basher83/lunar-claude/branch-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00659 |
| Opus 5.5 | $0.00004 | $0.00264 |
| Sonnet 5.5 | $0.00002 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
branch-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 2mo 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.
Perform a complete cleanup of local and remote branches after working on multiple PRs.
Current State
Default branch: !git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@' || echo "main"
Current branch: !git branch --show-current
Fetch latest: !git fetch --all --prune 2>&1
Branch Inventory
Local branches with tracking status:
!git branch --format='%(refname:short) %(upstream:track)' | sort
Recent branches by activity:
!git for-each-ref --count=15 --sort=-committerdate refs/heads/ --format='%(refname:short) - %(committerdate:relative)'
Remote branches:
!git branch -r --format='%(refname:short)' | grep -v HEAD | sort
Cleanup Candidates
Merged into default branch: !git branch --merged
Branches with gone remotes:
!git branch -vv | grep ': gone]' | awk '{print $1}' | sort
Protected Branches
Never delete branches matching these patterns:
main,master,develop,staging,productionrelease/*branches (unless explicitly confirmed)renovate/*branches (managed by Renovate bot)- Current working branch
- Branches with unpushed commits (confirm first)
Cleanup Workflow
Phase 1: Analyze
Review the branch inventory above. Categorize branches:
- Safe to delete: Merged branches and branches with gone remotes (excluding protected)
- Needs confirmation:
release/*branches, branches with unpushed commits - Protected: All protected branch patterns and current branch
Phase 2: Confirm Cleanup Plan
Present the cleanup plan and ask the user to select scope:
- All safe: Delete all merged and gone-remote branches
- Merged only: Delete only branches merged into default
- Gone only: Delete only branches with deleted remotes
- Review each: Confirm each branch individually
If "Review each" is selected, iterate through candidates asking per-branch confirmation.
Phase 3: Execute Cleanup
After confirmation, execute in order:
- Prune stale remote-tracking refs:
git remote prune origin - Delete merged local branches:
git branch -d <branch> - Delete gone-remote branches:
git branch -D <branch>
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.
- 2mo ago First seen · 94 lines · 11 tokens per session scan A 66b3ef32081a
branch-cleanup is a skill published in the GitHub repository basher83/lunar-claude (23 stars, last pushed today), licensed MIT. It adds 11 tokens to every session and 659 once invoked, about $0.0000 per session on Opus 5.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-30.
branch-cleanup compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| branch-cleanupbasher83/lunar-claude | Skill | 23 | today | MIT | A | 11 | Claude Code |
| merge-batchdiegosouzapw/OmniRoute | Skill | 85k | 2d ago | MIT | A | 46 | Claude Code |
| prowler-commitprowler-cloud/prowler | Skill | 15k | today | Apache-2.0 | A | 44 | Claude Code, Codex |
| gh-auth-isolationgithub/gh-aw | Skill | 5.6k | today | MIT | A | 20 | Claude Code, Codex |
| comet-githubrpamis/comet | Skill | 3.3k | today | MIT | A | 72 | Claude Code, Codex |
| github-skillzeenie-ai/OpenCompany | Skill | 1.1k | today | MIT | A | 51 | Claude Code |
| re0-mergeLilMGenius/paperthin | Skill | 1.4k | today | MIT | A | 51 | Claude Code, Codex |