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 motlin/claude-code-plugins/plugin install gitWrote 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/motlin/claude-code-plugins/git-cleanup)<a href="https://agentmods.dev/skills/motlin/claude-code-plugins/git-cleanup"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/git-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/motlin/claude-code-plugins/git-cleanup"><img src="https://agentmods.dev/badge/skills/motlin/claude-code-plugins/git-cleanup.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.00080 | $0.01092 |
| Opus 5.5 | $0.00032 | $0.00437 |
| Sonnet 5.5 | $0.00016 | $0.00218 |
| Haiku 4.5 | $0.00008 | $0.00109 |
Grade A, and why
git-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 3d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Cleanup
Use the code:cli and git:git-workflow skills.
Resolve <plugin-root> before running plugin scripts:
- In Claude Code, use
${CLAUDE_PLUGIN_ROOT}. - In Codex, use the plugin root that contains this
skills/git-cleanup/SKILL.mdfile.
Survey
Gather everything in one pass before changing anything:
git status --short --branch
git branch -vv
git worktree list
git stash list
git remote -v
git clean -nd
git clean -ndX
git count-objects -vH
For every local branch other than main, report commits ahead of and behind main, unmerged patches (git cherry main <branch> | grep -c '^+'), and last commit age. Read the diff of any uncommitted change so you can describe it.
Report and Ask
Summarize the findings in a few short lines, then ask with AskUserQuestion, one question per area that has something to decide:
- Uncommitted changes: commit on the current branch, commit on a new branch, or discard.
- Untracked files: add to
.gitignore, add to.git/info/excludefor files that are local to this machine (IDE folders,.llm/), commit them, or leave them. - Worktrees: for each worktree other than the main one, remove it, keep it, or decide each one. Show each worktree's branch and
git -C <worktree> status --short. A branch checked out in a worktree is skipped by the rebase. - Branches: rebase all, review each branch, or delete the backups and duplicates. Point out the likely candidates: names with
backup, near-identical names such asfix-loginandlogin-fix, and branches whose patches all appear in another branch.
Configure the Upstream Remote
The rebase and delete-merged scripts read UPSTREAM_REMOTE, which defaults to upstream. When git remote has no upstream and the project's .envrc does not set UPSTREAM_REMOTE, append the setting and re-allow it:
echo "export UPSTREAM_REMOTE=origin" >> .envrc
direnv allow .
The running shell does not reload .envrc, so also pass UPSTREAM_REMOTE=origin to the scripts in this session.
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.
- 3d ago First seen · 81 lines · 80 tokens per session scan A 9f34c653c9dd
git-cleanup is a skill published in the GitHub repository motlin/claude-code-plugins (20 stars, last pushed yesterday), licensed Apache-2.0. It adds 80 tokens to every session and 1,092 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-10-18.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.