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 ZaxbyHub/opencode-swarm --skill worktree-retry-cleanupgit clone --depth 1 https://github.com/ZaxbyHub/opencode-swarmWrote 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/zaxbyhub/opencode-swarm/worktree-retry-cleanup)<a href="https://agentmods.dev/skills/zaxbyhub/opencode-swarm/worktree-retry-cleanup"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/worktree-retry-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/zaxbyhub/opencode-swarm/worktree-retry-cleanup"><img src="https://agentmods.dev/badge/skills/zaxbyhub/opencode-swarm/worktree-retry-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.00043 | $0.00380 |
| Opus 5 | $0.00022 | $0.00190 |
| Sonnet 5 | $0.00009 | $0.00076 |
| Haiku 4.5 | $0.00004 | $0.00038 |
Grade C, and why
worktree-retry-cleanup 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 8d 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.
3. **Check for worktree directory:** if `.swarm-worktrees/<architect-session>` exists, remove it (`Remove-Item -Recurse -Force` / `rm -rf`) What it actually says
Worktree Retry Cleanup
Trigger
Before re-dispatching a coder for a task that already has a lane (any prior dispatch status).
Protocol
- Check for existing lane branch:
git branch --list "swarm/lane/<architect-session>/<task-id>" - If branch exists:
- Verify 0-commits-ahead:
git log --oneline HEAD..swarm/lane/<session>/<task>— empty = safe - Delete:
git branch -d swarm/lane/<session>/<task>(use-Donly if-dfails AND commits confirmed unneeded) - Under full-auto,
-Dis deny-pattern-blocked — use-d
- Verify 0-commits-ahead:
- Check for worktree directory: if
.swarm-worktrees/<architect-session>exists, remove it (Remove-Item -Recurse -Force/rm -rf) - Prune:
git worktree prune - Verify:
git branch --list "swarm/lane/<session>/<task>"returns empty - Only after cleanup, proceed to
declare_scope+ coder dispatch
Ownership validation
Before deleting, verify the worktree is not owned by another ACTIVE session. Check .swarm/session/state.json for concurrent sessions. If another session owns it, DO NOT delete — surface the conflict.
Root cause
The provisioning code should auto-clean after coder completion/denial/cancellation (tracked in issue #1746 item 1). This playbook is the temporary protocol.
What ships with it
1 file 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.
- 8d ago First seen · 27 lines · 43 tokens per session scan C 443da0610304
worktree-retry-cleanup is a skill published in the GitHub repository ZaxbyHub/opencode-swarm (467 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 380 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
armada-voyage-finish
Voyage-finalization ritual. Load at voyage end, dispatch a galleon subagent to rebase, fix TODO PR refs, regen scaffold, push, open/update PR. Triggers on: finish voyage, finalize, rebase, PR.
armada-pr
PR-first finish for a feature lane. Use before reporting a feature done. Triggers on: PR, finish feature, gh pr create, merge, lane complete.
github-cli
GitHub CLI (gh) wrapper for PR status, issues, and repository operations.
gitlab-cli
GitLab CLI (glab) wrapper for MR status, issues, and repository operations.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
prepare-pr
Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.