worktree

A command for creating and managing Git worktrees and their branches. A worktree is a separate working directory connected to the same Git repository.

In plain words
What is it for?
Creating, listing, inspecting, and removing worktrees, including worktrees based on ticket files.
Why use it?
It lets developers work on multiple branches in separate folders without repeatedly switching the main checkout. It also applies consistent branch names and safety checks.

Command

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.

agentmods
npx agentmods add commands/adrielp/ai-engineering-harness/worktree
Clone the repo
git clone --depth 1 https://github.com/adrielp/ai-engineering-harness
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 851 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00851
Opus 5 $0.00000 $0.00426
Sonnet 5 $0.00000 $0.00170
Haiku 4.5 $0.00000 $0.00085

Measured 2d ago against content hash 4a479f6654ba, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

opencode/commands/worktree.md · 107 lines

How it starts

The opening of the file, as written. The whole thing — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Git Worktree Manager

Conventions

Branch naming:

  • Ticket path → strip dir + .md, prefix feature/: thoughts/shared/tickets/add-auth.mdfeature/add-auth
  • Plain name → prefix feature/ unless already prefixed (fix/, chore/, etc.)

Worktree location: <repo-root>/../<repo-name>-worktrees/<branch-name> (sibling dir, outside main repo)

Default branch detection — never hardcode main:

DEFAULT_BRANCH=$(git symbolic-ref refs/remotes/origin/HEAD 2>/dev/null | sed 's|refs/remotes/origin/||') || DEFAULT_BRANCH="main"

Subcommand Dispatch

Parse the first argument. If none provided, print:

/worktree create <name|ticket-path>  — Create worktree + branch
/worktree list                       — All worktrees with dirty status
/worktree status                     — Detailed view (commits, ahead/behind)
/worktree remove <name>              — Remove with safety checks

Examples:
  /worktree create auth-refactor
  /worktree create thoughts/shared/tickets/add-auth.md

create

  1. Resolve branch name using naming conventions above. If argument is a ticket path, read the ticket for context.

  2. Check conflicts — run in parallel:

    git branch --list "<branch-name>"
    git worktree list
    

    If branch exists but has no worktree → offer git worktree add <path> <existing-branch> (no -b). If worktree already exists at path → show its location, ask if user wants to cd there instead.

  3. Create:

    REPO_ROOT=$(git rev-parse --show-toplevel)
    REPO_NAME=$(basename "$REPO_ROOT")
    WORKTREE_PATH="$REPO_ROOT/../${REPO_NAME}-worktrees/<branch-name>"
    mkdir -p "$(dirname "$WORKTREE_PATH")"
    git worktree add "$WORKTREE_PATH" -b <branch-name>
    
  4. Output: Branch, path, base ref, cd command. If from ticket, include ticket path.


list

Quick overview of all worktrees.

git worktree list --porcelain

Porcelain format — each worktree is a block separated by blank lines:

worktree /path/to/dir
HEAD <sha>
branch refs/heads/<name>

Read the full file on GitHub · 107 lines

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.

  1. 2d ago First seen · 107 lines · 0 tokens per session scan A 4a479f6654ba

Subscribe to this mod's changes

worktree is a command published in the GitHub repository adrielp/ai-engineering-harness (20 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 851 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.