Borrowing it
Nothing to install: this file belongs to julianoczkowski/notebooklm-mcp-2026. 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/julianoczkowski/notebooklm-mcp-2026/master/.claude/commands/cleanup-branches.mdgit clone --depth 1 https://github.com/julianoczkowski/notebooklm-mcp-2026Wrote 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/julianoczkowski/notebooklm-mcp-2026/cleanup-branches)<a href="https://agentmods.dev/commands/julianoczkowski/notebooklm-mcp-2026/cleanup-branches"><img src="https://agentmods.dev/badge/commands/julianoczkowski/notebooklm-mcp-2026/cleanup-branches/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/commands/julianoczkowski/notebooklm-mcp-2026/cleanup-branches"><img src="https://agentmods.dev/badge/commands/julianoczkowski/notebooklm-mcp-2026/cleanup-branches.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.00000 | $0.00330 |
| Opus 5 | $0.00000 | $0.00165 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
cleanup-branches 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 11d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- cleanup-branches — 100% identical, 0 lines differ
What it actually says
Clean up stale branches after merged PRs.
Instructions
You are cleaning up local and remote branches that are no longer needed. Follow these steps in order.
Step 1: List all branches
Run git branch -a to see all local and remote branches.
Identify branches that are NOT master or remotes/origin/master or remotes/origin/HEAD.
If there are no extra branches, tell the user everything is clean and stop.
Step 2: Show the user what will be deleted
List the branches grouped by:
- Local branches to delete
- Remote branches to delete
- Stale remote refs to prune
Ask the user to confirm before proceeding.
Step 3: Delete local branches
Delete all local branches except master:
git branch -d <branch1> <branch2> ...
If -d fails (unmerged branch), report it and ask the user if they want to force-delete with -D.
Step 4: Delete remote branches
For each remote branch (except master), delete it:
git push origin --delete <branch1> <branch2> ...
If a remote branch no longer exists (already deleted on GitHub), that's fine — proceed to pruning.
Step 5: Prune stale remote refs
git remote prune origin
Step 6: Verify
Run git branch -a and confirm only master and remotes/origin/master remain.
Report what was cleaned up.
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.
- 11d ago First seen · 55 lines · 0 tokens per session scan A e23c00051c20
cleanup-branches is a command published in the GitHub repository julianoczkowski/notebooklm-mcp-2026 (16 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 330 tokens. 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.
Other commands, from other repositories
CHANGELOG
Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.
mega-approve
Approve the mega-plan and start feature execution. Creates worktrees and generates PRDs for each feature. Usage: /plan-cascade:mega-approve [--flow ] [--tdd ] [--confirm] [--no-confirm] [--spec ] [--first-principles] [--max-questions N] [--auto-prd] [--agent ] [--prd-agent ] [--impl-agent ].
end
End the current collaboration session and release all claims.
improve
Run ONE iteration of the continuous-improvement loop — pick the highest-value backlog item, implement it, verify end-to-end, commit.
bulk-add
Batch-shelve several repos at once — from a URL list or your GitHub stars — then draft honest notes for each.
enable-journaling
Opt-in setup for auto-journaling capture plumbing. Copies bundled PostToolUse hook scripts into .squad/hooks/ and prints the exact .claude/settings.json snippet to wire them up. Capture-only — squad behaviour does NOT change until a follow-up release adds distillation + retrieval. Triggers: "enable journaling", "turn…