worktree-sync

worktree-sync is a command for Claude Code from kumaran-is/claude-code-onboarding. It costs 47 tokens per session (567 once invoked), scanned A, original, MIT.

A command for synchronising Git worktrees, which are separate directories for different branches of one repository. It can create a worktree for each open GitHub pull request or for a new branch.

In plain words
What is it for?
Use it to create and maintain local directories for open pull-request branches or a new branch.
Why use it?
It lets you work on several branches at once without stashing changes or repeatedly switching branches. Each branch can stay open in its own editor window.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to create and maintain local directories for open pull-request branches or a new branch.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/kumaran-is/claude-code-onboarding/worktree-sync
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/kumaran-is/claude-code-onboarding

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.

agentmods badge for worktree-sync

README.md
[![agentmods](https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/worktree-sync/github.svg)](https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/worktree-sync)
Your own site
<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/worktree-sync"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/worktree-sync/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.

agentmods 80×15 button for worktree-sync

Your own site · 80×15
<a href="https://agentmods.dev/commands/kumaran-is/claude-code-onboarding/worktree-sync"><img src="https://agentmods.dev/badge/commands/kumaran-is/claude-code-onboarding/worktree-sync.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 567 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.00567
Opus 5 $0.00023 $0.00283
Sonnet 5 $0.00009 $0.00113
Haiku 4.5 $0.00005 $0.00057

Measured 5d ago against content hash b466aaedf409, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

worktree-sync 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 5d 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.

.claude/commands/worktree-sync.md · 70 lines

What it actually says

Worktree Sync

Create and maintain git worktrees so each open PR branch has its own directory on disk. No stashing. No context switching. Open multiple editor windows on different branches simultaneously.

Step 1 — Determine Mode

If $ARGUMENTS contains --new <branch-name>: skip to Step 3 (create one new branch + worktree). Otherwise: run Step 2 (sync all open PRs).

Step 2 — Sync All Open PR Worktrees

# Verify GitHub CLI auth
gh auth status

# Create worktree base directory
mkdir -p ./tree

# Create a worktree for each open PR branch
gh pr list --json headRefName --jq '.[].headRefName' | while read branch; do
  safe_name="${branch//\//-}"
  branch_path="./tree/$safe_name"
  if [ ! -d "$branch_path" ]; then
    echo "Creating worktree: $branch → $branch_path"
    git fetch origin "$branch" 2>/dev/null || true
    git worktree add "$branch_path" "$branch"
  else
    echo "Already exists: $branch_path (skipping)"
  fi
done

git worktree list

After sync: open each ./tree/<branch>/ in a separate terminal or editor window. Each directory is a full independent working copy sharing the same .git object store.

Step 3 — Create New Branch + Worktree

Use when starting a new feature branch and wanting an isolated working directory from day one.

# branch_name comes from --new argument (e.g. --new feature/auth)
branch_name="<extract branch name from $ARGUMENTS after --new>"
repo_root=$(git rev-parse --show-toplevel)
parent_dir=$(dirname "$repo_root")
safe_branch="${branch_name//\//-}"
worktree_path="$parent_dir/$(basename "$repo_root")-$safe_branch"

git worktree add -b "$branch_name" "$worktree_path"
echo "Worktree created at: $worktree_path"
echo "Open this directory in a separate editor window to work in parallel."
git worktree list

Step 4 — Prune Stale Worktrees

If a worktree directory was deleted manually, clean up the dangling reference:

git worktree prune
git worktree list

$ARGUMENTS

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. 5d ago First seen · 70 lines · 0 tokens per session scan A b466aaedf409

Subscribe to this mod's changes

worktree-sync is a command published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 567 once invoked, about $0.0002 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.