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 nirecom/agents --skill sweep-worktreesgit clone --depth 1 https://github.com/nirecom/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/nirecom/agents/sweep-worktrees)<a href="https://agentmods.dev/skills/nirecom/agents/sweep-worktrees"><img src="https://agentmods.dev/badge/skills/nirecom/agents/sweep-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/nirecom/agents/sweep-worktrees"><img src="https://agentmods.dev/badge/skills/nirecom/agents/sweep-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.00033 | $0.00846 |
| Opus 5.5 | $0.00013 | $0.00338 |
| Sonnet 5.5 | $0.00007 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade C, and why
sweep-worktrees scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
`git worktree remove` (if still registered) or `rm -rf` (if not registered How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reclaims zombie linked worktrees left behind when /worktree-end could not
physically remove a worktree (e.g. Windows CWD lock from VS Code's extension
host). After successful worktree removal, also deletes the corresponding
branch. Also scans WORKTREE_BASE_DIR for orphan directories not tracked by
git's worktree registry.
Procedure
SWT-1. Resolve $AGENTS_MAIN_ROOT from the environment; abort with a clear error
if unset.
SWT-2. Invoke the sweeper script, forwarding the user's flags verbatim:
bash "$AGENTS_MAIN_ROOT/bin/sweep-worktrees.sh" [--dry-run] [--force] [--min-age-hours N] [--ci-mode]
SWT-3. Print the script's stdout verbatim. Do not summarize or filter.
Add no flags of your own.
Rules
- Deletes by default;
--dry-runmust be explicit to preview only. --forcepasses--forcetogit worktree remove, bypassing the dirty-tree check; PR-merged and freshness gates still apply.- EPERM / busy / not-empty failures on a per-worktree basis are non-fatal: warning printed, that worktree skipped, sweep continues.
- Branch deletion (
git branch -D) is authorized only AFTER the worktree is removed (git's cascade rule blocks branch deletion while the worktree is registered). - Detached HEAD worktrees are skipped with a warning (no branch ⇒ no PR
merged check, no
branch -Dtarget). - A 4-AND safety check is required before any deletion: registered linked
worktree AND PR merged AND clean working tree (bypassed by
--force) AND mtime > threshold. - Orphan-directory scan uses a 4-AND gate: containment under WORKTREE_BASE_DIR
AND no .git AND mtime > threshold AND ownership proof via
Main repo:field inWORKTREE_NOTES.md. Basename match alone is NOT ownership proof — two unrelated repos can shareagents/dotfilesbasenames. The former "empty-or-notes-only" gate was removed: a partialgit worktree removecan leave a full checkout without a .git file, which is safe to delete when ownership is proven. - Before each worktree and orphan-directory removal the sweeper releases that path's own CodeGraph index lock. No-op when the flag is off, when no index exists, or when the tool is absent; a daemon whose own argv does not name exactly this path is reported, never killed.
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 Changed 9256c69ec073
- 23d ago Changed · -2 lines 6be9966ce0d1
- 1mo ago Changed · +3 lines ea44586e0378
- 1mo ago First seen · 66 lines · 33 tokens per session scan C 6210bf857ba9
sweep-worktrees is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 846 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). 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.