stale-branches

stale-branches is a command for Claude Code from joaquimscosta/arkhe-claude-plugins. It costs 14 tokens per session (295 once invoked), scanned A, original, MIT.

A read-only Git command that lists branches that may no longer be needed, such as merged branches or branches with no recent commits. Git is the version-control system used to track code changes and branches.

In plain words
What is it for?
Use it to inspect local or remote branches, check inactivity against a chosen time threshold, and compare branches with a base branch such as main.
Why use it?
Old branches clutter repositories and make active work harder to find. It identifies cleanup candidates without deleting anything.

Command for Claude Code

Written for Claude Code: argument-hint in frontmatter.

Good fit Use it to inspect local or remote branches, check inactivity against a chosen time threshold, and compare branches with a base branch such as main.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/joaquimscosta/arkhe-claude-plugins/stale-branches
Install

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.

Clone the repo
git clone --depth 1 https://github.com/joaquimscosta/arkhe-claude-plugins

Made for: Claude Code.

Wrote 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.

agentmods badge for stale-branches

README.md
[![agentmods](https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/stale-branches/github.svg)](https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/stale-branches)
Your own site
<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/stale-branches"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/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.

agentmods 80×15 button for stale-branches

Your own site · 80×15
<a href="https://agentmods.dev/commands/joaquimscosta/arkhe-claude-plugins/stale-branches"><img src="https://agentmods.dev/badge/commands/joaquimscosta/arkhe-claude-plugins/stale-branches.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 295 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00014 $0.00295
Opus 5.5 $0.00006 $0.00118
Sonnet 5.5 $0.00003 $0.00059
Haiku 4.5 $0.00001 $0.00030

Measured yesterday against content hash 6fb0c33412ee, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

plugins/git/commands/stale-branches.md · 39 lines

What it actually says

Stale Branches

List local and remote git branches that are candidates for cleanup — merged but not deleted, and inactive branches with no recent commits.

Usage

/stale-branches [options]

Options

  • --threshold <months> - Inactivity threshold in months (default: 3)
  • --base <branch> - Base branch for merge check (default: main)
  • --remote - Include remote branch analysis

Examples

/stale-branches                          # Default: 3 months, main, local only
/stale-branches --threshold 1            # Stricter: 1 month inactivity
/stale-branches --remote                 # Include remote branches
/stale-branches --base develop           # Use develop as base branch
/stale-branches --threshold 1 --remote   # Combine flags

Implementation

Invoke the Skill tool with skill name "git:listing-stale-branches" and arguments: $ARGUMENTS

The skill will detect merged branches, inactive unmerged branches, and optionally analyze remote branches. It is read-only and never deletes branches.

For detailed documentation, see git/skills/listing-stale-branches/SKILL.md.

Changes

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.

  1. yesterday First seen · 39 lines · 14 tokens per session scan A 6fb0c33412ee

Subscribe to this mod's changes

stale-branches is a command published in the GitHub repository joaquimscosta/arkhe-claude-plugins (21 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 295 once invoked, about $0.0001 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.