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/ruizrica/toolkit/worktreegit clone --depth 1 https://github.com/ruizrica/toolkitWhat 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.00459 |
| Opus 5 | $0.00000 | $0.00230 |
| Sonnet 5 | $0.00000 | $0.00092 |
| Haiku 4.5 | $0.00000 | $0.00046 |
Grade A, and why
worktree 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.
What it actually says
/worktree
Create an isolated development worktree with automatic branch and path generation.
Usage
/worktree # Auto-create with timestamp-based branch (wip-YYYYMMDD-HHMMSS)
/worktree [path] # Custom path, auto-generated branch
/worktree [path] [branch] # Custom path and branch
Commands
/worktree- Quick start: creates worktree with auto-generated wip-YYYYMMDD-HHMMSS branch/worktree [path] [branch]- Advanced: specify custom path and branch
Both versions run setup automation:
- Installs dependencies (npm, pnpm, yarn, or pip)
- Copies
.env.exampleto.env(if present) - Opens
$EDITOR/$VISUALwhen available
Why this command exists
Provides isolated development environments using git worktrees. The simple form (no args) auto-generates a timestamp-based wip branch for quick starts, while the full form allows custom naming.
Behavior
-
/worktree(no arguments):- Generates branch name:
wip-YYYYMMDD-HHMMSS - Creates worktree at:
.specbook/worktrees/wip-YYYYMMDD-HHMMSS - No interactive prompts - fully automatic
- Generates branch name:
-
/worktree [path] [branch](with arguments):- Uses specified path and/or branch
- When only path provided, auto-generates branch name
- When branch doesn't exist, creates it with
git worktree add -b - Rolls back created worktree/branch if setup fails
Error handling
- Not in a git repository: command fails early.
- Bad args: usage is displayed.
- Missing branch for default operations: falls back to fuzzy/interactive selection.
Setup automation summary format
Creating worktree: <path> (<branch>)
Environment: .env prepared (if .env.example exists)
Editor launch: attempted (if editor variables are set)
See Also
/setup- repository initialization + memory indexing/save- merge and clean up worktree workflows
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 · 58 lines · 0 tokens per session scan A 1b7603e48573
worktree is a command published in the GitHub repository ruizrica/toolkit (5 stars, last pushed 17d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 459 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-31.
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.