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.
git clone --depth 1 https://github.com/forrestchang/worktree-workflowWrote 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/commands/forrestchang/worktree-workflow/done)<a href="https://agentmods.dev/commands/forrestchang/worktree-workflow/done"><img src="https://agentmods.dev/badge/commands/forrestchang/worktree-workflow/done/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/commands/forrestchang/worktree-workflow/done"><img src="https://agentmods.dev/badge/commands/forrestchang/worktree-workflow/done.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.00000 | $0.00630 |
| Opus 5.5 | $0.00000 | $0.00252 |
| Sonnet 5.5 | $0.00000 | $0.00126 |
| Haiku 4.5 | $0.00000 | $0.00063 |
Grade A, and why
done 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/done - Complete work on an issue
Help the developer wrap up their work on the current issue.
Usage
/done # Complete the issue detected from branch name
/done ISSUE-12 # Complete a specific issue
Dependencies
- Optional:
linearCLI for Linear integration - Optional:
ghCLI for GitHub PR creation
Steps
- Detect the issue from the branch name or use the provided ID
- Detect base branch for comparison:
base=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's@^refs/remotes/origin/@@') # Fallback to main/master - Summarize the work by checking:
git log --oneline $base..HEADto see commitsgit diff --stat $base..HEADto see files changed
- Ask what they want to do:
- Create PR and close
- Close issue (no PR)
- Add notes and close
- Just clean up (keep issue open)
After Selection
If they want to create a PR:
- Run
gh pr create --title "ISSUE-12: Issue title" --body "..."with a summary - Then proceed to closing if requested
If they want to add notes (requires linear CLI):
- Ask what notes to add
- Run
linear issue update ISSUE-12 --append "..."with the notes
If they want to close (requires linear CLI):
- Run
linear done ISSUE-12to close the issue
Worktree cleanup:
If in a worktree, offer commands to clean up:
# Get worktree info
repo_root=$(git rev-parse --show-toplevel)
repo_name=$(basename "$repo_root")
branch_name=$(git branch --show-current)
# Convert slashes in branch name to dashes for directory name
dir_safe_branch="${branch_name//\//-}"
worktrees_dir="$(dirname "$repo_root")/worktrees"
worktree_path="$worktrees_dir/${repo_name}-${dir_safe_branch}"
# From main repo, remove the worktree
cd <main-repo-path>
git worktree remove "$worktree_path"
git worktree prune
Example Flow
User: /done
Claude: Let me check what you've been working on...
[Runs git log and git diff]
You've made 3 commits on ISSUE-12: Add caching layer
- src/cache.ts (new file, 45 lines)
- src/api.ts (modified, +12 -3)
[Presents options above]
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 · 87 lines · 0 tokens per session scan A ceca1503ddce
done is a command published in the GitHub repository forrestchang/worktree-workflow (108 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 630 tokens. 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-30.
Other commands, from other repositories
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
land
Resolve and squash merge one named, currently authorized pull request.
sync-coordinator
Multi-package synchronization and version alignment with ruv-swarm coordination for seamless integration between claude-code-flow and ruv-swarm packages.
github-modes
This document describes all GitHub integration modes available in Claude-Flow with ruv-swarm coordination. Each mode is optimized for specific GitHub workflows and includes batch tool integration for maximum efficiency.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
ship
Deliver one goal end to end (clarify, implement, PR, review, CI, merge) via the ship skill.