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 ivy00johns/Skill-Madness --skill git-post-merge-cleanupgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/git-post-merge-cleanup)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/git-post-merge-cleanup"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/git-post-merge-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/ivy00johns/skill-madness/git-post-merge-cleanup"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/git-post-merge-cleanup.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.00194 | $0.01764 |
| Opus 5 | $0.00097 | $0.00882 |
| Sonnet 5 | $0.00039 | $0.00353 |
| Haiku 4.5 | $0.00019 | $0.00176 |
Grade A, and why
git-post-merge-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 10d 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 — 199 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Post-Merge Cleanup
After a batch of PRs land, the local repo accumulates debris: fully merged branches, tracking refs whose remote was deleted by GitHub, and worktrees that still show "modified" files even though those changes are already on main. This skill cleans all of it in one pass — scan, classify, present a plan, confirm, execute. The scan is cheap; always do both classes.
Flags
--dry-run— scan and present the plan, but do not delete anything.--yes— skip the confirmation prompt. Still presents the plan first.
Default (no flags): scan, present plan, wait for confirmation.
Step 1 — Refresh remote state
git fetch origin --prune
Without --prune, stale origin/* refs linger for branches GitHub already
deleted on merge.
Step 2 — Detect the default branch
Do not assume main:
git symbolic-ref -q --short refs/remotes/origin/HEAD 2>/dev/null | sed 's@^origin/@@'
If that fails, fall back to checking whether main or master exists
locally. Use the result as $DEFAULT.
Step 3 — Scan and classify
Run both classifiers. Results feed the single plan in Step 4.
Branches
Cross-reference: git branch -vv (tracking status), git branch --merged origin/$DEFAULT (local merged), git branch -r --merged origin/$DEFAULT
(remote merged), git branch -r --no-merged origin/$DEFAULT (context).
Bucket every branch into one of:
- fully-merged-local — in
--merged, not the default branch. Safe togit branch -d. - fully-merged-remote — in
-r --merged, notorigin/HEADand notorigin/$DEFAULT. Safe togit push origin --delete. - orphan-tracking —
git branch -vvshows tracking remote asgoneAND branch is not in--merged. Unmerged work; flag for user attention, do not delete. - in-flight — everything else. Leave alone.
See references/branch-classification.md for edge cases (squash-merged
branches that don't appear in --merged, detached HEAD, etc).
Worktrees
git worktree list
What ships with it
2 files 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.
- 10d ago First seen · 199 lines · 194 tokens per session scan A 6e87da0854a8
git-post-merge-cleanup is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 2d ago), licensed MIT. It adds 194 tokens to every session and 1,764 once invoked, about $0.0010 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-30.
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…
nvca-chart-release
Release NVCA Operator chart changes from the native monorepo source to the vendored Helm chart. Use when updating the vendored NVCA Operator chart, changing NVCA image refs, publishing helm-nvca-operator, or validating the chart against a self-managed control plane.