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 rsenna/rs-agent-plugin --skill git-branch-hygienegit clone --depth 1 https://github.com/rsenna/rs-agent-pluginWrote 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/rsenna/rs-agent-plugin/git-branch-hygiene)<a href="https://agentmods.dev/skills/rsenna/rs-agent-plugin/git-branch-hygiene"><img src="https://agentmods.dev/badge/skills/rsenna/rs-agent-plugin/git-branch-hygiene/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/rsenna/rs-agent-plugin/git-branch-hygiene"><img src="https://agentmods.dev/badge/skills/rsenna/rs-agent-plugin/git-branch-hygiene.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.00079 | $0.01920 |
| Opus 5.5 | $0.00032 | $0.00768 |
| Sonnet 5.5 | $0.00016 | $0.00384 |
| Haiku 4.5 | $0.00008 | $0.00192 |
Grade A, and why
git-branch-hygiene 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 1mo 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Branch Hygiene
The pull-request-process skill's cleanup step only removes the one
worktree/branch a task just finished with — and only when explicitly run,
right after a PR merges. In practice that step gets skipped constantly
(session ends before merge, user moves on, a new session starts cold), so
local branches and pr.sh start worktrees pile up silently across many
sessions. This skill is the periodic sweep that catches all of that at
once, for the whole repo — not a replacement for pull-request-process's
per-task cleanup, a backstop for when it didn't happen.
Core principle
Classify everything before touching anything. A branch merged via a
squash or true-merge PR is NOT an ancestor of main by git's own ancestry
check — relying on git branch --merged alone silently mis-classifies
those as unmerged. Always cross-check against the forge's actual PR state
(gh pr list --head <branch>) when available, and only fall back to the
ancestor check for branches with no PR record at all.
Never delete on inference. A branch with real commits and no PR record might be abandoned scratch work — or it might be someone's still-relevant draft that never got pushed. A worktree with uncommitted files is never safe to force-remove, no matter how old it looks. Every ambiguous case gets surfaced to the user; only clearly-merged branches get deleted without individual confirmation (and even then, as one batch confirmation showing the full list — see Step 3).
Step 1: Run the audit
audit.sh is a sibling of whatever directory this SKILL.md was loaded
from — resolve it there rather than assuming a fixed install root (e.g.
~/.claude/skills/git-branch-hygiene/audit.sh,
~/.agents/skills/git-branch-hygiene/audit.sh, or a project-local
.agents/skills/git-branch-hygiene/audit.sh, depending on how this skill
was installed).
A=<this-skill's-own-directory>/audit.sh
"$A" [base-branch]
Read-only — fetches origin (no --prune, so it never deletes remote-tracking refs), then classifies every local branch
and its worktree (if any) into four buckets:
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 147 lines · 79 tokens per session scan A 208a1944d82a
git-branch-hygiene is a skill published in the GitHub repository rsenna/rs-agent-plugin (2 stars, last pushed 2d ago), licensed MIT. It adds 79 tokens to every session and 1,920 once invoked, about $0.0003 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-09-15.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.