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 shousper/claude-kit --skill worktree-cleanupgit clone --depth 1 https://github.com/shousper/claude-kitWrote 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/shousper/claude-kit/worktree-cleanup)<a href="https://agentmods.dev/skills/shousper/claude-kit/worktree-cleanup"><img src="https://agentmods.dev/badge/skills/shousper/claude-kit/worktree-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/shousper/claude-kit/worktree-cleanup"><img src="https://agentmods.dev/badge/skills/shousper/claude-kit/worktree-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.00091 | $0.01238 |
| Opus 5.5 | $0.00036 | $0.00495 |
| Sonnet 5.5 | $0.00018 | $0.00248 |
| Haiku 4.5 | $0.00009 | $0.00124 |
Grade A, and why
worktree-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 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Cleanup
Overview
Clean up a git worktree after work is complete (merged, PR created, or abandoned). Updates the mainline branch so local state is current.
Core principle: User-triggered only. Never automatic.
The Process
Step 1: List Worktrees
git worktree list
If multiple worktrees exist (beyond the main working tree), present the list and ask which to clean up.
If only one non-main worktree exists, confirm: "Remove worktree at <path>?"
Step 2: Check for Uncommitted Changes
git -C <worktree-path> status --porcelain
If dirty:
- Show the uncommitted files
- Ask: "This worktree has uncommitted changes. Proceed with removal? (Changes will be lost)"
- Require explicit confirmation
Step 3: Remove Worktree
⚠️ CRITICAL — cd before removal: You MUST determine the main working tree path and cd to it BEFORE running any removal command. Always chain the cd and removal in the SAME shell call using &&. Never run them as separate shell calls — shell CWD persists between calls, but a deleted CWD will brick every subsequent command.
First, capture the main working tree path from Step 1's output (the first entry in git worktree list).
Then remove:
cd <main-working-tree> && git worktree remove <worktree-path>
If removal fails (e.g., locked or dirty), try with --force after informing your human partner:
cd <main-working-tree> && git worktree remove --force <worktree-path>
If the worktree directory was already manually deleted from disk, clean up stale metadata:
cd <main-working-tree> && git worktree prune
Recovery: Dead CWD
If any Bash command fails with Path "..." does not exist, your shell CWD has been deleted from disk. Do NOT retry the same command. You MUST prefix your next command with an absolute cd:
cd <main-working-tree> && git worktree prune && git worktree list
The main working tree path (first entry from Step 1) is always valid. Use that. Retrying without the cd prefix will fail infinitely.
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 · 148 lines · 91 tokens per session scan A be2798626e26
worktree-cleanup is a skill published in the GitHub repository shousper/claude-kit (4 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 1,238 once invoked, about $0.0004 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
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.