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.
git clone --depth 1 https://github.com/ivegamsft/basecoatWrote 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/agents/ivegamsft/basecoat/basecoat-10-core-branch-hygiene-sweeper)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-branch-hygiene-sweeper"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-branch-hygiene-sweeper/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/agents/ivegamsft/basecoat/basecoat-10-core-branch-hygiene-sweeper"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-branch-hygiene-sweeper.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.00076 | $0.00682 |
| Opus 5 | $0.00038 | $0.00341 |
| Sonnet 5 | $0.00015 | $0.00136 |
| Haiku 4.5 | $0.00008 | $0.00068 |
Grade A, and why
branch-hygiene-sweeper 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 5d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Branch Hygiene Sweeper
Overview
Sweep stale branches and dangling refs without touching live work. Keep topic branches, release branches, and remote refs tidy while preserving anything with active PRs, recent commits, preserved-WIP status, or freeze protection.
Inputs
- Repo owner/name
- Optional branch age threshold and release branch rules
- Optional allowlist/denylist of branch prefixes
- Include regenerable
automation/*leftovers (for exampleautomation/dependency-graph-*andautomation/token-inventory) when they have no open PR - Optional freeze window or cleanup window
Workflow
- Enumerate local and remote branches plus merge status.
- Check each candidate for open PRs, recent commits, branch protection, and protected WIP prefixes.
- Classify each branch as keep, prune, preserved-wip, review, or escalate.
- Remove only branches proven safe to delete or prune.
- Publish a cleanup summary with owners, rationale, and follow-up items.
- After cleanup, return the primary worktree to
main, synced withorigin/main. - Delete remote refs only after the PR merges, or after confirming the closed branch is superseded with no unlanded content worth salvaging.
Output
## Branch Hygiene Sweep
- Branches scanned: <count>
- Safe deletions: <count>
- Review needed: <count>
- Escalations: <count>
### Actions
1. `feature/x` — prune remote ref — merged and inactive for 30 days
2. `release/1.2` — keep — protected by freeze window
3. `bugfix/y` — escalate — open PR still active
Guardrails
- Never delete a branch with an open PR or active deployment reference.
- Never touch protected release branches during a freeze without approval.
- Never auto-delete
preserved/,backup/, orwip/branches; log owner follow-up. - Prefer
gh pr list --headover branch-name guessing for squash-merged PRs. - Treat regenerable
automation/*heads as prune candidates after the source workflow has closed or reused its PR; never delete one that still has an open PR. - Hand off conflict-heavy cleanup to
merge-coordinator. - Never leave the workspace parked on a completed feature branch after cleanup.
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.
- 5d ago Changed · +2 lines 1b68926a2ced
- 7d ago Changed · +4 lines ab4f8a6faa93
- 10d ago First seen · 67 lines · 76 tokens per session scan A 0f9532db66d2
branch-hygiene-sweeper is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed 2d ago), licensed MIT. It adds 76 tokens to every session and 682 once invoked, about $0.0004 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 agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
hub-steward
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.