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 joaquimscosta/arkhe-claude-plugins --skill listing-stale-branchesgit clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-pluginsWrote 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/joaquimscosta/arkhe-claude-plugins/listing-stale-branches)<a href="https://agentmods.dev/skills/joaquimscosta/arkhe-claude-plugins/listing-stale-branches"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/listing-stale-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/skills/joaquimscosta/arkhe-claude-plugins/listing-stale-branches"><img src="https://agentmods.dev/badge/skills/joaquimscosta/arkhe-claude-plugins/listing-stale-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.00100 | $0.02566 |
| Opus 5.5 | $0.00040 | $0.01026 |
| Sonnet 5.5 | $0.00020 | $0.00513 |
| Haiku 4.5 | $0.00010 | $0.00257 |
Grade A, and why
listing-stale-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 today.
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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stale Branch Detection
Identify git branches that are candidates for cleanup: merged-but-not-deleted and inactive branches with no recent commits.
Auto-Invoke Triggers
This skill automatically activates when:
- Keywords: "stale branches", "old branches", "branch cleanup", "prune branches", "dead branches", "unused branches", "inactive branches", "branch hygiene"
- Actions: "list branches to delete", "find stale branches", "clean up branches"
Arguments
--threshold <months>— Inactivity threshold in months (default: 3)--base <branch>— Base branch for merge check (default: main)--remote— Include remote branch analysis
Workflow
Execute each step below using the Bash tool. This is a read-only skill — never delete branches, only report findings.
Step 1: Validate Git Repository
git rev-parse --is-inside-work-tree 2>/dev/null || echo "NOT_A_GIT_REPO"
If not a git repo, stop and inform the user.
Step 2: Parse Arguments
Parse $ARGUMENTS for:
--threshold N→ set THRESHOLD_MONTHS=N (default: 3)--base BRANCH→ set BASE_BRANCH=BRANCH (default: main)--remote→ set INCLUDE_REMOTE=true (default: false)
Verify the base branch exists:
git rev-parse --verify "$BASE_BRANCH" 2>/dev/null || echo "BASE_BRANCH_NOT_FOUND"
If the base branch doesn't exist, try master as fallback. If neither exists, stop and inform the user.
Step 3: Calculate Inactivity Threshold
Cross-platform threshold date (epoch seconds):
# macOS
if [[ "$OSTYPE" == "darwin"* ]]; then
threshold=$(date -v-${THRESHOLD_MONTHS}m +%s)
else
# Linux
threshold=$(date -d "${THRESHOLD_MONTHS} months ago" +%s)
fi
echo "Threshold date (epoch): $threshold"
Step 4: List Merged Branches
Find local branches already merged into the base branch (safe to delete):
echo "=== MERGED BRANCHES (safe to delete) ==="
merged_count=$(git branch --merged "$BASE_BRANCH" | grep -v "^\*" | grep -vw "$BASE_BRANCH" | wc -l | tr -d ' ')
git branch --merged "$BASE_BRANCH" | grep -v "^\*" | grep -vw "$BASE_BRANCH" | while IFS= read -r branch; do
branch="${branch## }"
last_commit_date=$(git log -1 --format='%ci' "$branch" 2>/dev/null | cut -d' ' -f1)
echo " $branch (last commit: ${last_commit_date:-unknown})"
done
if [ "$merged_count" -eq 0 ]; then
echo " (none)"
fi
echo "Total merged: $merged_count"
What ships with it
3 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.
- today First seen · 242 lines · 100 tokens per session scan A 49a88c77e634
listing-stale-branches is a skill published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed today), licensed MIT. It adds 100 tokens to every session and 2,566 once invoked, about $0.0004 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-10-16.
Other skills, from other repositories
git-workflow
Git branching, commits, and PR workflow following GitFlow conventions.
pr-creator
Create well-structured pull requests with proper descriptions and labels.
diff-project
Shows what changed in dotforge since the project's last sync, to decide whether running /forge sync is worthwhile.
finish
Ship phase — merge, PR, keep, or discard with pre-merge verification.
dev-finish
Close out a session — summarise what changed, capture what was learned, and prepare the commit.
dev-rc
The last gate before merge — QA, security audit, review and changelog, with objective pass conditions.