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 vincentkoc/dotskills --skill org-branch-cleanupgit clone --depth 1 https://github.com/vincentkoc/dotskillsWrote 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/vincentkoc/dotskills/org-branch-cleanup)<a href="https://agentmods.dev/skills/vincentkoc/dotskills/org-branch-cleanup"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/org-branch-cleanup/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/vincentkoc/dotskills/org-branch-cleanup"><img src="https://agentmods.dev/badge/skills/vincentkoc/dotskills/org-branch-cleanup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.01096 |
| Opus 5 | $0.00046 | $0.00548 |
| Sonnet 5 | $0.00018 | $0.00219 |
| Haiku 4.5 | $0.00009 | $0.00110 |
Grade A, and why
org-branch-cleanup 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 11d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Org Branch Cleanup
Purpose
Remove organization branch clutter without guessing which refs are safe to delete.
The bundled scripts/org_branch_cleanup.py separates the work into read-only audit, explicit apply, and full verification phases. Dry-run evidence is the default; deletion requires an exact organization confirmation.
When to use
- A GitHub organization has accumulated old or merged development branches.
- Bot, agent, migration, or dependency branches remain after pull requests merge.
- A maintainer wants an evidence-backed cleanup ledger rather than broad
git push --delete. - Branch-heavy security, state, archive, or generated-data repositories need to be separated from ordinary development repos.
- A previous cleanup stopped midway and must resume without repeating completed deletions.
Workflow
- Read the target repository or organization instructions before mutation.
- Confirm GitHub authentication and rate-limit headroom:
gh auth statusgh api rate_limit --jq '.resources | {core,graphql}'
- Run a read-only audit:
Start withpython3 scripts/org_branch_cleanup.py audit \ --org example-org \ --output /tmp/example-org-branch-audit--include-repo-regex '^one-repo$'when proving access or policy. Audit output is immutable by default; use a new directory rather than--overwrite. - Inspect
audit-summary.json,audit-errors.tsv, anddelete-candidates.jsonl.- Do not apply a partial audit. Fix failed repository queries or explicitly justify
--allow-partial. - Default candidates are same-repository PR heads merged at least 14 days ago.
- Closed-unmerged branches and unassociated stale branches are report-only.
- Default, fork, archived, protected, and release-like refs are excluded.
- Repositories matching GHSA, state, or archive patterns are excluded by default. Audit them separately under an explicit retention policy.
- Do not apply a partial audit. Fix failed repository queries or explicitly justify
- Apply only after the candidate set is reviewed:
python3 scripts/org_branch_cleanup.py apply \ --candidates /tmp/example-org-branch-audit/delete-candidates.jsonl \ --confirm-org example-org \ --output /tmp/example-org-branch-applyapplyrequires the clean siblingaudit-summary.json. Do not bypass this with--allow-unverified-candidatesor--allow-partial-auditwithout an explicit operator decision. - Treat each preflight skip as a safety result, not a failure.
moved: branch SHA changed after the snapshot.protected: REST or ruleset protection blocked deletion.open-pr: a live pull request now uses the branch.missing: GitHub or another operator already removed it.
- Verify every deletion:
python3 scripts/org_branch_cleanup.py verify \ --ledger /tmp/example-org-branch-apply/deleted.tsv \ --output /tmp/example-org-branch-apply/verification-rerun.tsv - Report exact deleted, skipped, retained, excluded-repository, and verification counts. Preserve the ledger until the cleanup is accepted.
What ships with it
4 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.
- 11d ago First seen · 88 lines · 91 tokens per session scan A e4b11204475f
org-branch-cleanup is a skill published in the GitHub repository vincentkoc/dotskills (102 stars, last pushed yesterday), licensed MIT. It adds 91 tokens to every session and 1,096 once invoked, about $0.0005 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 skills, from other repositories
taiyi-integration
A project workflow skill for closing a TaiyiForge change and recording it in a CHANGELOG.md file. It checks review results, tests, and the state of the working tree before archiving the change.
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
linear-cli
Use when the user wants to list, view, start, create, or update Linear issues from the terminal via schpet/linear-cli, including setup, auth, repo config, and safe read/write boundaries.
github-commenting
How to post clean, rich, deduplicated GitHub PR review comments — suggestion blocks, multi-line anchors, markers, formatting rules. Load before posting or fixing any PR comment.
git-checkout-cache
Cache and refresh remote git repositories under /.cache/checkouts/ / / for reuse. Use when the user points you to a remote git repository as reference, or when you need to read, search or analyze a remote repo locally without full clone overhead.
git-workflow
Git workflow assistant for branching, PRs, and conflict resolution. Use when the user asks about git strategy, branch management, PR workflow, or needs non-interactive git operations.