Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bengous/claude-code-plugins/plugin install git-sweepWrote 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/bengous/claude-code-plugins/git-sweep)<a href="https://agentmods.dev/skills/bengous/claude-code-plugins/git-sweep"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/git-sweep/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/bengous/claude-code-plugins/git-sweep"><img src="https://agentmods.dev/badge/skills/bengous/claude-code-plugins/git-sweep.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.00854 |
| Opus 5.5 | $0.00030 | $0.00342 |
| Sonnet 5.5 | $0.00015 | $0.00171 |
| Haiku 4.5 | $0.00008 | $0.00085 |
Grade A, and why
git-sweep 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 1mo 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Sweep
Route to the correct cleanup phase based on repo state. The phase files
audit.md and apply.md live in this skill's base directory.
Inputs
- base: $ARGUMENTS
(optional: the base branch to audit against, e.g.
/git-sweep dev; empty lets the backend resolve the trunk: git config sweep.base, then origin/HEAD, then main/master/trunk) - branch: !
git branch --show-current - repo: !
git rev-parse --show-toplevel - worktrees: !
git worktree list - pending: !
test -f "$(git rev-parse --absolute-git-dir)/git-sweep-manifest.json" && echo "yes" || echo "no" - tools: !
test -x "${CLAUDE_PLUGIN_ROOT}/scripts/git-clean-audit.ts" && test -x "${CLAUDE_PLUGIN_ROOT}/scripts/git-clean-apply.ts" && echo "ok" || echo "missing"
Routing
if tools == "missing":
STOP — tell user: git-clean-audit and/or git-clean-apply not executable.
Run: chmod +x "${CLAUDE_PLUGIN_ROOT}/scripts/git-clean-audit.ts" "${CLAUDE_PLUGIN_ROOT}/scripts/git-clean-apply.ts"
if pending == "yes":
# A previous run left operations unexecuted (partial failure, or an
# interrupted hand-off). The file holds an already-confirmed selection.
AskUserQuestion:
header: "Manifest"
question: "A pending cleanup manifest exists. Apply it, or re-audit?"
options: "Apply pending manifest (Recommended)"
| "Re-audit (overwrites it)"
if "Apply pending manifest":
Read apply.md and follow it
(do not continue below)
Read audit.md and follow it
The audit phase handles all "nothing to clean" detection itself (local branches, remote branches, worktrees). Do not short-circuit here.
Configuration (git config, all optional)
sweep.base— trunk to audit against when no argument is givensweep.protect(multi-valued) — extra branches never proposed for deletionsweep.unprotect(multi-valued) — lift names from the default protected set (main, master, trunk, dev, develop); the audited base stays protectedsweep.agentPrefix/sweep.backupPrefix— classification prefixes (defaultsworktree-agent-,backup/; they must not overlap)sweep.maxAgeDays— age bound for the containment test (default 180)
What ships with it
2 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.
- 1mo ago First seen · 85 lines · 76 tokens per session scan A f234a0f85f32
git-sweep is a skill published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed yesterday), licensed MIT. It adds 76 tokens to every session and 854 once invoked, about $0.0003 per session on Opus 5.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
flow-next-land
Resolve feedback and CI for one named pull request, then merge when authorized and ready. Emits LANDVERDICT. Use when asked to land a pull request.
flow-next-worktree-kit
Manage git worktrees (create/list/switch/cleanup) and copy .env files. Use for parallel feature work, isolated review, clean workspace, or when user mentions worktrees.
development-workflow
Detailed development workflow with modular patterns for git, review, testing, and deployment.
stepwise-task-execution
Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a needrevision bounce.
github-cli
A command-line tool connection for GitHub tasks that built-in tools do not cover. It uses GitHub's command-line program to work with issues, pull requests, releases, workflows, searches, and the GitHub API.
incremental-commits
Commit boundaries and messages on a task branch. Use when deciding where to cut a commit or how to word one while implementing.