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 tomzx/agents --skill prune-merged-worktreesgit clone --depth 1 https://github.com/tomzx/agentsWrote 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/tomzx/agents/prune-merged-worktrees)<a href="https://agentmods.dev/skills/tomzx/agents/prune-merged-worktrees"><img src="https://agentmods.dev/badge/skills/tomzx/agents/prune-merged-worktrees/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/tomzx/agents/prune-merged-worktrees"><img src="https://agentmods.dev/badge/skills/tomzx/agents/prune-merged-worktrees.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.00079 | $0.01833 |
| Opus 5.5 | $0.00032 | $0.00733 |
| Sonnet 5.5 | $0.00016 | $0.00367 |
| Haiku 4.5 | $0.00008 | $0.00183 |
Grade A, and why
prune-merged-worktrees 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 22d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prune Merged Worktrees
Finds local git worktrees whose branch's remote was deleted, verifies through GitHub that the branch's pull request was actually merged, then removes the worktree and the local branch after user confirmation.
Verification goes through the forge because squash and rebase merges (the /merge-pr default) land the work under a new SHA, so git branch -d, git merge-base --is-ancestor, and git rev-list main..<branch> all classify fully shipped branches as unmerged.
Prerequisites
- Current working directory is a checkout of the target repository, or a repo path is passed as
$1 git worktreeavailableghx(preferred) orghCLI authenticated with access to the repository- The skill never removes the main checkout, a bare entry, or the worktree containing the current directory
Arguments and Flags
$1(optional): path to the repository checkout (default: current directory)--dry-run: print the classification table and exit without removing anything--force: allow removing worktrees with uncommitted changes; without it, dirty worktrees are reported and skipped
Steps
1. List worktrees and candidates
git -C <repo> worktree list --porcelain
Skip the main checkout (the first entry) and any worktree containing the current directory.
For each remaining worktree, read its branch from the branch line.
2. Fetch and find stale branches
git -C <repo> fetch --prune origin
git -C <repo> branch -vv
A worktree is a candidate only when its branch's upstream is gone (the remote branch was deleted, typically by the merge).
Worktrees whose upstream still exists (open PRs, shared branches) are kept.
Worktrees on branches with no upstream at all were never pushed, so there is no PR to verify: report them as skipped.
3. Verify merge state against GitHub
For each candidate branch, list merged PRs from that head.
ghx pr list does not expose headRefOid, so use gh:
gh pr list --state merged --head <branch> --json number,headRefOid,mergedAt
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.
- 22d ago Changed · +8 lines 2c8d538b8a24
- 25d ago Changed 1157ebcb4373
- 27d ago Changed · -1 lines 88289e831a9b
- 1mo ago First seen · 160 lines · 79 tokens per session scan A f487e6ad0c5e
prune-merged-worktrees is a skill published in the GitHub repository tomzx/agents (13 stars, last pushed yesterday), licensed MIT. It adds 79 tokens to every session and 1,833 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-09-23.
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.