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 fang2hou/skills --skill git-branch-cleanupgit clone --depth 1 https://github.com/fang2hou/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/skills/fang2hou/skills/git-branch-cleanup)<a href="https://agentmods.dev/skills/fang2hou/skills/git-branch-cleanup"><img src="https://agentmods.dev/badge/skills/fang2hou/skills/git-branch-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.1 | $0.00046 | $0.04431 |
| Opus 5 | $0.00023 | $0.02216 |
| Sonnet 5 | $0.00009 | $0.00886 |
| Haiku 4.5 | $0.00005 | $0.00443 |
Grade A, and why
git-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 8d 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Branch Cleanup
Remove local worktrees and branches whose changes are provably absorbed somewhere else — nothing else — and only after the user approves each group.
Two independent groups are produced, because their risk differs:
- Group 1 — landed: the work is on the remote default branch. Deleting loses nothing; the remote holds it.
- Group 2 — absorbed locally: the work is in the branch currently checked out in this worktree (the integration branch) but not yet on the remote default. Deleting loses nothing as long as that integration branch survives.
A branch in Group 1 or Group 2 is a candidate. Every other branch is non-deletable here and is only reported.
When to Use
- After merging pull requests, especially squash merges.
- After a fan-out agent session that left
worktree/*or feature branches and worktree directories behind (e.g. herdr-managed worktrees), including ones already merged into the integration branch the agent is standing on. - The user asks to clean up branches or worktrees, delete merged branches, or list what is safe to remove.
When NOT to Use
- Deleting remote branches — out of scope; remotes are read-only here.
- Cleaning stashes, tags, or reflog entries.
- Any repository where the user has not confirmed the deletion list.
- Forcing removal of a dirty, locked, or unreadable worktree — always reported, never forced.
Inputs
| Input | Required | Format | Example |
|---|---|---|---|
| Remote name | No (default origin) |
git remote name | upstream |
| Integration branch | No (default current HEAD) | local branch | feature/integration |
| Dry run | No (flag in user request) | request phrasing | user asks to only show a plan |
Hard Rules
- Never delete before the user confirms the exact list. Group 1 and Group 2 are confirmed separately; approving one never implies the other. No batch shortcuts, no "obviously safe" exceptions.
[gone]upstream alone NEVER qualifies a branch for deletion. A remote branch can be deleted while the work is unmerged.[gone]is only a hint to run the merge checks.- Detect the default branch from
<remote>/HEAD, never hardcodemain/master. If unset, rungit remote set-head <remote> --autofirst. - A branch belongs to Group 1 only if it passes at least one of, against
DEFAULT:- Check A: it is an ancestor of
DEFAULT(ordinary merge) - Check B:
git cherry DEFAULT <branch>prints only-lines (every commit patch-equivalent — single-commit squash merges) - Check C: a merged PR whose head ref is this branch has
headRefOidequal to the local tip ANDbaseRefNameequal to the short name ofDEFAULT— the merged PR is provably THIS branch state, landed on THIS target
- Check A: it is an ancestor of
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.
- 8d ago First seen · 248 lines · 46 tokens per session scan A b9083480e9e9
git-branch-cleanup is a skill published in the GitHub repository fang2hou/skills (2 stars, last pushed 21d ago), licensed MIT. It adds 46 tokens to every session and 4,431 once invoked, about $0.0002 per session on Opus 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-31.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
codex-autoresearch
Run autonomous, measurable experiments in a Git repository: change one hypothesis, verify a numeric metric, keep improvements, and revert failures. Use when the user wants Codex to keep iterating toward a numeric target in the foreground or as a detached background run. Do not use for ordinary one-shot coding…