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 agentmods add commands/rjwalters/kicad-tools/branchesgit clone --depth 1 https://github.com/rjwalters/kicad-toolsWrote 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/commands/rjwalters/kicad-tools/branches)<a href="https://agentmods.dev/commands/rjwalters/kicad-tools/branches"><img src="https://agentmods.dev/badge/commands/rjwalters/kicad-tools/branches.svg" alt="Measured on agentmods" 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.00024 | $0.04352 |
| Opus 5 | $0.00012 | $0.02176 |
| Sonnet 5 | $0.00005 | $0.00870 |
| Haiku 4.5 | $0.00002 | $0.00435 |
Grade A, and why
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 6d 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 — 368 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/repo:branches — Branch & Worktree Hygiene
Find stale local branches and worktrees that can be safely removed. Reports findings and waits for confirmation before deleting anything.
Usage
/repo:branches # Full audit
/repo:branches --prune # Delete confirmed-safe branches after reporting
Steps
1. Inventory
Gather current state:
# Default branch
git symbolic-ref --short refs/remotes/origin/HEAD 2>/dev/null | sed 's|origin/||'
# Count local branches
git branch --list | wc -l
# List worktrees
git worktree list
# Identify active worktree branches (these are PROTECTED)
git worktree list --porcelain | grep '^branch ' | sed 's|branch refs/heads/||'
2. Categorize branches
For every local branch, classify it into one of these buckets:
PROTECTED (never delete)
- The default branch (
main/master) and the currently checked-out branch - Any branch currently checked out by a worktree
- Any branch with an open PR:
gh api "repos/{owner}/{repo}/pulls?state=open&head={owner}:<branch>" --jq length - Long-lived branches the repo's own docs (CLAUDE.md, CONTRIBUTING.md) name as release/project branches — if such a list exists, honor it
MERGED PR BRANCHES
- Branches matching common PR patterns:
feature/*,fix/*,feat/*,pr-* - Check whether a PR exists for the branch's head and is merged (the REST form
below) — a count
>= 1means the branch is safe to delete - Also safe: any branch fully merged into the default branch
(
git branch --merged <default>). Reachability is sufficient but not necessary — a squash-merged branch is never--merged, so its absence from that list means nothing. Step 5 decides.
gh api "repos/{owner}/{repo}/pulls?state=all&head={owner}:<branch>" \
--jq '[.[] | select(.merged_at != null)] | length'
REST's pulls endpoint has no state=merged value — only open, closed, and
all — so merged-ness is a client-side filter on .merged_at != null over
state=all. An older closed-but-unmerged PR on the same head is correctly
excluded by it. Step 5b arm 4 runs the same call for the final verdict.
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.
- 6d ago First seen · 368 lines · 24 tokens per session scan A ddacd6fa5a5e
branches is a command published in the GitHub repository rjwalters/kicad-tools (55 stars, last pushed yesterday), licensed MIT. It adds 24 tokens to every session and 4,352 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.