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 agentmods add commands/forrestchang/worktree-workflow/donegit clone --depth 1 https://github.com/forrestchang/worktree-workflowWhat 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 | $0.00000 | $0.00630 |
| Opus 5 | $0.00000 | $0.00315 |
| Sonnet 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 2d 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.
- 2d ago First seen · 87 lines · 0 tokens per session scan A ceca1503ddce
done is a command published in the GitHub repository forrestchang/worktree-workflow (109 stars, last pushed 7mo 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.