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 jamesyang124/agent-skills --skill git-stale-branch-cleanupgit clone --depth 1 https://github.com/jamesyang124/agent-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/jamesyang124/agent-skills/git-stale-branch-cleanup)<a href="https://agentmods.dev/skills/jamesyang124/agent-skills/git-stale-branch-cleanup"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/git-stale-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/jamesyang124/agent-skills/git-stale-branch-cleanup"><img src="https://agentmods.dev/badge/skills/jamesyang124/agent-skills/git-stale-branch-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.00079 | $0.01149 |
| Opus 5 | $0.00039 | $0.00575 |
| Sonnet 5 | $0.00016 | $0.00230 |
| Haiku 4.5 | $0.00008 | $0.00115 |
Grade A, and why
git-stale-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 12d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Stale Branch Cleanup
Two modes — both always generate a full scan report before any action:
- Dry-run (default): scan → report only, nothing deleted.
- Live: scan → report → multi-select → confirm → delete remote → prune local.
Usage
/git-stale-branch-cleanup # prompts for mode
/git-stale-branch-cleanup --dry-run
/git-stale-branch-cleanup --live
Arguments
All optional.
| Token / flag | Meaning |
|---|---|
--dry-run |
scan and report only, nothing deleted (default) |
--live |
scan, report, then multi-select and delete |
| a bare integer | staleness threshold in days (Phase 2) |
| any other bare token | base branch, e.g. origin/main (Phase 1) |
Anything not passed is asked for in its phase prompt.
Reference Scripts
Run directly — do not regenerate these commands inline. Agent instructions are embedded in each script header; read them after running.
| Script | Run as |
|---|---|
references/scan-pass-a.sh |
bash references/scan-pass-a.sh "$BASE_BRANCH" "$THRESHOLD_DAYS" "$SCAN_LIMIT" |
references/scan-pass-b.sh |
bash references/scan-pass-b.sh "<branch>" "$BASE_BRANCH" |
references/delete-branch.sh |
bash references/delete-branch.sh "<branch>" |
⚠ BLOCKING: Load mode file before proceeding
If Live mode / --live:
→ read_file: .agent-settings/skills/git-stale-branch-cleanup/references/mode-live.md
If Dry-run / --dry-run / default:
→ No extra file needed — dry-run exits after Phase 4.
Phase 0 — Mode Selection
[D] Dry-run (default) — scan and report only, nothing deleted
[L] Live — scan, report, then select branches to delete
Select mode [D/L]:
Default (Enter) → Dry-run. Load mode file immediately per BLOCKING rule above.
Phase 1 — Base Branch
[1] origin/main (default)
[2] origin/master
[3] origin/develop
[4] Other — type the branch name
Select [1-4]:
Auto-detect default via git remote show origin | grep 'HEAD branch'. Store as BASE_BRANCH.
Then: git fetch --prune origin
What ships with it
4 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.
- 12d ago First seen · 157 lines · 79 tokens per session scan A 029ad4898e14
git-stale-branch-cleanup is a skill published in the GitHub repository jamesyang124/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 79 tokens to every session and 1,149 once invoked, about $0.0004 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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
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…