What is create-git-worktree?

A command for creating a Git worktree and branch. A worktree is a separate directory connected to the same Git project, allowing another branch to be worked on independently.

Use it to create a branch in a new directory under trees/, switch into it, and verify the active branch.

It lets you work on a separate branch without replacing the files in your current project directory.

create-git-worktree — Command for Claude Code by marmot-protocol

Install

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.

Clone the repo

git clone --depth 1 https://github.com/marmot-protocol/agent-config

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/marmot-protocol/agent-config/create-git-worktree/github.svg)](https://agentmods.dev/commands/marmot-protocol/agent-config/create-git-worktree)

Your own site

<a href="https://agentmods.dev/commands/marmot-protocol/agent-config/create-git-worktree"><img src="https://agentmods.dev/badge/commands/marmot-protocol/agent-config/create-git-worktree/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/marmot-protocol/agent-config/create-git-worktree"><img src="https://agentmods.dev/badge/commands/marmot-protocol/agent-config/create-git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 359 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00008	$0.00359
Opus 5.5	$0.00003	$0.00144
Sonnet 5.5	$0.00002	$0.00072
Haiku 4.5	$0.00001	$0.00036

Measured 1mo ago against content hash e1d9d043ffac, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

create-git-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 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.

opencode/commands/create-git-worktree.md · 65 lines

What it actually says

Create Git Worktree

Create a new git worktree in the trees/ directory with the branch name provided as the argument.

CRITICAL: This is a ONE-SHOT command

DO NOT ask any questions - use $ARGUMENTS as the branch name directly
The branch name IS the argument - no clarification needed
Execute all steps automatically without prompting

Execution Steps

1. Get Branch Name

The branch name is: $ARGUMENTS

If $ARGUMENTS is empty, report an error: "Usage: /create-git-worktree "

2. Create Worktree Directory

mkdir -p trees

3. Create the Worktree

Run this command from PROJECT_CWD:

git worktree add trees/$ARGUMENTS -b $ARGUMENTS 2>/dev/null || git worktree add trees/$ARGUMENTS $ARGUMENTS

This handles both cases:

If the branch doesn't exist: creates it with -b
If the branch already exists: checks it out in the worktree

4. Verify Creation

git worktree list | grep "trees/$ARGUMENTS"

5. Switch to the Worktree

This is essential - change into the new worktree directory:

cd trees/$ARGUMENTS

6. Confirm Ready

Report success with the current working directory and branch:

pwd
git branch --show-current

Tell the user they are now in the worktree and ready to work.

Changes

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 · 65 lines · 8 tokens per session scan A e1d9d043ffac

Subscribe to this mod's changes

create-git-worktree is a command published in the GitHub repository marmot-protocol/agent-config (2 stars, last pushed 8mo ago), licensed MIT. It adds 8 tokens to every session and 359 once invoked, about $0.0000 per session on Opus 5.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-08-31.

Git and workflow

create-git-worktree