worktree-status

A project command that lists every Git worktree, a separate working directory linked to the same repository, with its branch, clean or changed state, and latest commit.

In plain words
What is it for?
Use it to inspect all active worktrees, or use verbose mode to see the last three commits for each one.
Why use it?
It gives a single view of parallel branches and shows which working directories have uncommitted changes. This makes it easier to avoid overlooking work in another worktree.

Command for Claude Code

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/brain-bootstrap/claude-code-brain-bootstrap/worktree-status
Clone the repo
git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrap

Made for: Claude Code.

Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 698 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.00018 $0.00698
Opus 5 $0.00009 $0.00349
Sonnet 5 $0.00004 $0.00140
Haiku 4.5 $0.00002 $0.00070

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

Security

Grade A, and why

worktree-status 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.

.claude/commands/worktree-status.md · 108 lines

How it starts

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

Worktree Status

Show all active git worktrees with their branch, dirty/clean status, and last commit.

Usage

/worktree-status           # Show all worktrees
/worktree-status verbose   # Include last 3 commits per worktree

Implementation

Execute this script:

#!/bin/bash
set -euo pipefail

VERBOSE=false
if [[ "${ARGUMENTS:-}" == *"verbose"* ]]; then
  VERBOSE=true
fi

GIT_COMMON_DIR="$(git rev-parse --git-common-dir 2>/dev/null)"
if [ -z "$GIT_COMMON_DIR" ]; then
  echo "Not in a git repository"
  exit 1
fi

echo "Git Worktrees"
echo "============="
echo ""

COUNT=0
while IFS= read -r line; do
  if [[ "$line" =~ ^([^[:space:]]+)[[:space:]]+([0-9a-f]+)[[:space:]]+\[(.+)\]$ ]]; then
    WT_PATH="${BASH_REMATCH[1]}"
    WT_COMMIT="${BASH_REMATCH[2]}"
    WT_BRANCH="${BASH_REMATCH[3]}"

    # Check dirty status
    if git -C "$WT_PATH" diff --quiet 2>/dev/null && git -C "$WT_PATH" diff --cached --quiet 2>/dev/null; then
      STATUS="clean"
    else
      CHANGED=$(git -C "$WT_PATH" status --short 2>/dev/null | wc -l | xargs)
      STATUS="dirty ($CHANGED files)"
    fi

    # Short commit hash
    SHORT_HASH="${WT_COMMIT:0:7}"

    echo "  Branch: $WT_BRANCH"
    echo "  Path:   $WT_PATH"
    echo "  Status: $STATUS"
    echo "  Commit: $SHORT_HASH"

    if [ "$VERBOSE" = true ]; then
      echo "  Recent commits:"
      git --no-pager -C "$WT_PATH" log --oneline -3 2>/dev/null | sed 's/^/    /' || true
    fi

    echo ""
    COUNT=$((COUNT + 1))
  fi
done < <(git worktree list 2>/dev/null)

echo "Total: $COUNT worktree(s)"
echo ""
echo "Create:  /worktree <branch>"
echo "Cleanup: /clean-worktrees"

Output Example

Git Worktrees
=============

  Branch: main
  Path:   /home/user/myproject
  Status: clean
  Commit: 9982075

  Branch: feature/new-ui
  Path:   /home/user/myproject/.worktrees/feature-new-ui
  Status: dirty (3 files)
  Commit: a1b2c3d

Total: 2 worktree(s)

Create:  /worktree <branch>
Cleanup: /clean-worktrees

Read the full file on GitHub · 108 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 · 108 lines · 18 tokens per session scan A 8282ede4c3fd

Subscribe to this mod's changes

worktree-status is a command published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 4mo ago), licensed MIT. It adds 18 tokens to every session and 698 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-08-30.