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 ostin-pil/aboard --skill prune-branchesgit clone --depth 1 https://github.com/ostin-pil/aboardWrote 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/ostin-pil/aboard/prune-branches)<a href="https://agentmods.dev/skills/ostin-pil/aboard/prune-branches"><img src="https://agentmods.dev/badge/skills/ostin-pil/aboard/prune-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.00022 | $0.00984 |
| Opus 5 | $0.00011 | $0.00492 |
| Sonnet 5 | $0.00004 | $0.00197 |
| Haiku 4.5 | $0.00002 | $0.00098 |
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 7d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-merge hygiene. This repo's workflow (work on feature/session-N-* / track-* branches → PR from the ostin-pil fork → merge commit on GitHub → pull main) leaves stale local branches every cycle. They clog git branch and produce confusing git status "ahead N" lines because they still track the now-merged PR head.
The non-obvious trap this skill exists to encode: git branch -d will refuse a fully-merged branch ("not fully merged") when that branch's upstream is the stale/merged PR head — even though the branch is merged into main (HEAD). git branch --merged main is the truth; for branches it lists, -D is safe even when -d balks.
Argument
$ARGUMENTS — optional --yes to skip the force-delete confirmation (non-interactive use). Anything else is ignored.
Preconditions — all must hold; abort (delete nothing) otherwise
- On
main.git branch --show-currentismain. Else abort: "switch to main first — pruning runs from main". main==origin/main.git fetch origin mainthengit rev-list --left-right --count origin/main...mainis0 0.- Behind → abort: "local main is behind origin/main; pull first — 'merged into main' would be measured against a stale main".
- Ahead → abort: "local main has unpushed commits; resolve first".
- Clean tree.
git status --porcelainis empty. Else abort.
Abort = print the reason and stop. No deletions on a stale or dirty main.
Steps
- Compute the merged set (source of truth).
git branch --merged main | grep -vE '^\*| main$'(trim whitespace). This is the only set eligible for deletion. Empty → print "no merged local branches to prune" and stop. - Record recovery SHAs. For each candidate,
git rev-parse --short <branch>. Print the name→SHA table and note: recoverable for ~90 days viagit branch <name> <sha>/git reflog. - Safe pass (batch). Run
git branch -don all candidates in one command. Capture which wereDeletedand which were refused ("not fully merged"). - Reconcile refusals. Every refused branch must still be in the step-1 merged set —
-drefused only because the upstream is the stale PR head, not because of unmerged work. Computerefused ∖ merged-set: it must be empty. If any refused branch is not in the merged set, that is an anomaly — do not delete it; report it and keep it. - Force pass (verified subset only). If the refused-but-merged subset is non-empty, confirm via
AskUserQuestion(skip the prompt if--yeswas passed). The confirm option's description must explain why it is safe — e.g. "Refused by-donly because their upstream is the stale pre-merge PR head, not because they hold unmerged work;git branch --merged mainconfirms they are in main; local-only; recoverable via reflog." On confirm:git branch -D <subset>. On decline: keep them, report. - Report. Deleted (with SHAs), force-deleted (with SHAs), kept and why. Confirm
git branch -ris unchanged — origin is never touched.
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.
- 7d ago First seen · 44 lines · 22 tokens per session scan A e74eed2e9027
prune-branches is a skill published in the GitHub repository ostin-pil/aboard (0 stars, last pushed 9d ago), licensed Apache-2.0. It adds 22 tokens to every session and 984 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-31.
Other skills, from other repositories
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts) and an annotated tag. Verify, commit, tag. Stops at "committed and tagged locally" — no push, no publish. The release-and-publish skill picks up from here. Distilled…
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, pushes commits and tags, then publishes to each applicable destination. Assumes git wrapup (version bumps, changelog, commit, annotated tag) is already…
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.