Borrowing it
Nothing to install: this file belongs to loerei/chronicle-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/loerei/chronicle-mcp/main/.agents/skills/prune-branches/SKILL.mdgit clone --depth 1 https://github.com/loerei/chronicle-mcpWrote 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/loerei/chronicle-mcp/prune-branches)<a href="https://agentmods.dev/skills/loerei/chronicle-mcp/prune-branches"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/prune-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/loerei/chronicle-mcp/prune-branches"><img src="https://agentmods.dev/badge/skills/loerei/chronicle-mcp/prune-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.00035 | $0.00615 |
| Opus 5 | $0.00017 | $0.00308 |
| Sonnet 5 | $0.00007 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00061 |
Grade A, and why
prune-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 9d 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 — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prune Branches
Audit-first branch pruning. ALWAYS report findings and await explicit user approval before deleting branches.
Workflow
flowchart TD
Start["Prune Request"] --> Fetch["1. Sync: git fetch --all --prune"]
Fetch --> DetectDefault["2. Detect default branch: main / master"]
DetectDefault --> Audit["3. Scan merged & deep-review unmerged branches"]
Audit --> Report["4. Present Audit Report & Recommendations"]
Report --> Choice{"User Approves Deletion?"}
Choice -->|"No"| Stop["STOP - No deletions made"]
Choice -->|"Yes"| Switch["5. Switch off target branch if active"]
Switch --> Delete["6. Delete local (-d/-D) & remote (--delete)"]
Delete --> Resync["7. Resync: git fetch --all --prune"]
Branch Classification Heuristics
| Category | Detection Command / Condition | Action / Recommendation |
|---|---|---|
| Directly Merged | git branch --merged <default> / git branch -r --merged origin/<default> |
Mark safe to delete |
| Squash-Merged | git diff origin/<default>...origin/<branch> --stat is empty (0 insertions, 0 deletions), OR git cherry returns - |
Mark safe to delete (Squash-merged) |
| Unmerged Active | git cherry returns + and tree diff has changes |
Recommend: 1. PR & Merge, 2. Cherry-pick, or 3. Abandon |
Execution Protocol
1. Audit (Read-Only)
- Detect Default Branch:
git symbolic-ref refs/remotes/origin/HEAD(fallback tomain). - Sync Tracking Refs:
git fetch --all --prune. - Audit Branches: Run merged commands and deep-review unmerged branches against the table above.
- Report & Await Approval: Output categorized branch lists (Directly Merged, Squash-Merged, Active Unmerged). STOP and await explicit user confirmation.
2. Prune (Post-Approval Only)
- Active Branch Guard: If current branch is targeted for deletion, switch first:
git checkout <default>. - Delete Local:
git branch -d <branch>(use-Donly for confirmed squash-merged branches). - Delete Remote:
git push origin --delete <branch1> <branch2> ... - Resync Tracking Cache:
git fetch --all --prune.
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.
- 9d ago First seen · 46 lines · 35 tokens per session scan A a1bd30de5f2b
prune-branches is a skill published in the GitHub repository loerei/chronicle-mcp (0 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 615 once invoked, about $0.0002 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.
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.