Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/arrrrny/zuraffa/speckit.worktrees.create)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.worktrees.create"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.worktrees.create.svg" alt="Measured on agentmods" 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.00017 | $0.01191 |
| Opus 5 | $0.00009 | $0.00596 |
| Sonnet 5 | $0.00003 | $0.00238 |
| Haiku 4.5 | $0.00002 | $0.00119 |
Grade A, and why
speckit.worktrees.create 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Worktree
Spawn an isolated git worktree for a feature branch so you can work on multiple features — or run multiple agents — in parallel without switching branches.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty). The user may specify:
- A branch name (e.g.,
005-user-auth) currentto create a worktree for the current branch--in-placeor--no-worktreeto skip worktree creation entirely
Prerequisites
- Verify the project is a git repository (
git rev-parse --show-toplevel) - Verify
git worktreeis available (git worktree listsucceeds)
Git extension (optional): The Spec Kit Git extension’s before_specify → speckit.git.feature checks out the feature branch on the current tree. For parallel agents on one primary clone, maintainers recommend disabling that hook in .specify/extensions.yml and relying on git worktree add -b (this script) so the primary HEAD stays put. See the extension README Parallel agents and the Git extension.
Configuration
Read configuration from .specify/extensions/worktrees/worktree-config.yml if it exists. Defaults apply when the file is absent.
| Key | Default | Description |
|---|---|---|
layout |
nested |
nested — worktree at .worktrees/<branch>/ inside repo (self-contained); sibling — at ../<repo>--<branch> (IDE-friendly) |
auto_create |
true |
When true, the after_specify hook creates a worktree without prompting |
sibling_pattern |
{{repo}}--{{branch}} |
Name pattern for sibling directories |
dotworktrees_dir |
.worktrees |
Subdirectory name for nested layout |
Environment variable SPECIFY_WORKTREE_PATH overrides the computed path entirely.
Outline
- Determine target branch:
- If user specifies a branch name, use that
- If user says
current, use the output ofgit branch --show-current - If no input and this is an
after_specifyhook call, use the branch that/speckit.specifyjust created (read fromSPECIFY_FEATUREenv var or the most recent feature branch) - Validate the branch exists in git (local or remote)
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 · 100 lines · 17 tokens per session scan A bf64954df59d
speckit.worktrees.create is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 1,191 once invoked, about $0.0001 per session on Opus 5. 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-09-03.
Other commands, from other repositories
building-flutter-apps-skill-ac1294fc
Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.
sdlc
Route a task to the next synced SDLC workflow based on current artifacts and repo state.
plan-feature
Plan a feature from BRD-lite brief or clear intent into PRD (What), decisions, implementation plan, and task slices.
bundle-analyze
Tu es un expert performance React. Tu dois analyser la taille du bundle, identifier les dépendances volumineuses et proposer des optimisations.
daily-standup
Génération Résumé Daily Stand-up.
generate-adapter
Erstellt ein Paperclip-Extension-Gerüst (Plugin via create-paperclip-plugin oder Built-in-Adapter).