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 hxy91819/mason-skills --skill worktree-cleanupgit clone --depth 1 https://github.com/hxy91819/mason-skillsWrote 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/hxy91819/mason-skills/worktree-cleanup)<a href="https://agentmods.dev/skills/hxy91819/mason-skills/worktree-cleanup"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/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/hxy91819/mason-skills/worktree-cleanup"><img src="https://agentmods.dev/badge/skills/hxy91819/mason-skills/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.00034 | $0.01064 |
| Opus 5 | $0.00017 | $0.00532 |
| Sonnet 5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00106 |
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 11d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Cleanup
Run this workflow only when the user explicitly invokes $worktree-cleanup. It performs repository-wide discovery and can remove worktrees. Always audit first, present the exact candidates, and apply only the approval tokens the user selects.
Requirements
Require Git, Python 3.10+, GitHub CLI, and an authenticated gh session with read access to the repository's pull requests. Run from a repository checkout or pass --repo <path>.
Audit
-
Check the current branch,
git status --short, andgit worktree list. Preserve concurrent and unrelated work. -
Create a new temporary report path outside the repository and run the helper in dry-run mode:
python3 <skill-dir>/scripts/cleanup_worktrees.py \ --repo <repo-path> \ --dry-run \ --json \ --write-approval-report <temporary-report.json> -
Review every candidate and skip reason. A candidate is eligible only when all of these hold:
- Git status is known and clean, including untracked files.
- The worktree is neither locked nor marked prunable.
- It is not the primary checkout or the checkout selected by
--repo. - Its exact HEAD is contained in the remote head of a merged or closed GitHub pull request; or no pull request exists, the worktree is at least 24 hours old by default, and its HEAD is either the tip of a GitHub remote branch or contained in the remote default branch.
-
Review
ignored.discarded_sampleandignored.discarded_countfor every candidate. These count ignored path roots, not files or bytes; one listed directory may contain substantial data..localis backed up; all other ignored files are deliberately discarded if that candidate is approved. -
Tell the user the exact paths, whether each path is managed or external, remote durability proof, ignored data impact, backup base directory, and all retained paths with their reasons. Ask once whether to remove all listed candidates or a named subset; do not make the user copy or re-approve token strings. Worktrees outside
.worktrees/follow the same eligibility rules.
What ships with it
3 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.
- 11d ago First seen · 76 lines · 34 tokens per session scan A 82de8f413008
worktree-cleanup is a skill published in the GitHub repository hxy91819/mason-skills (2 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,064 once invoked, about $0.0002 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 skills, from other repositories
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.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…