worktree-list

A diagnostic command for listing Git worktrees, which are multiple working folders linked to one repository, along with development-track details.

In plain words
What is it for?
Checking Git worktrees, Claude worktree folders, legacy development tracks, and the related SQLite state database.
Why use it?
It helps investigate where parallel development copies live and whether their tracking information is available.

Skill for Claude CodeCodex

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 skills/michael-harris/devteam/worktree-list
Any agent
npx skills add michael-harris/devteam --skill worktree-list
Clone the repo
git clone --depth 1 https://github.com/michael-harris/devteam

Made for: Claude Code, Codex.

Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 993 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.00023 $0.00993
Opus 5 $0.00012 $0.00496
Sonnet 5 $0.00005 $0.00199
Haiku 4.5 $0.00002 $0.00099

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

Security

Grade A, and why

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

skills/worktree-list/SKILL.md · 143 lines

How it starts

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

Git worktrees: !git worktree list 2>/dev/null || echo "Not a git repository" Native worktrees: !ls -d .claude/worktrees/*/ 2>/dev/null || echo "None" Legacy worktrees: !ls -d .multi-agent/track-*/ 2>/dev/null || echo "None" State DB exists: !test -f .devteam/devteam.db && echo "yes" || echo "no"

Worktree List Command

Debug/Expert Command - List all git worktrees with development track information.

Note: This command is rarely needed. Worktrees are managed automatically by /devteam:implement. Use this only for debugging worktree issues.

Command Usage

/devteam:worktree list           # List all worktrees

Your Process

Step 1: Get Git Worktrees

# Get all git worktrees
git worktree list --porcelain

Step 2: Load State from SQLite

Query the SQLite database (.devteam/devteam.db) to correlate git worktrees with development tracks:

source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"
# Track info available via get_state "parallel_tracks.track_info.*"

Step 3: Display Worktree Information

Git Worktrees

Mode: Git worktrees enabled
State database: .devteam/devteam.db

Main Repository:
Path: /home/user/my-project
Branch: main
HEAD: abc123 (2 hours ago)

Development Track Worktrees:

Track 01: Backend API
  Path: /home/user/my-project/.multi-agent/track-01
  Branch: dev-track-01
  HEAD: def456 (30 min ago)
  Status: Complete (2/2 sprints)
  Size: 45 MB

Track 02: Frontend
  Path: /home/user/my-project/.multi-agent/track-02
  Branch: dev-track-02
  HEAD: ghi789 (1 hour ago)
  Status: In Progress (1/2 sprints)
  Size: 52 MB

Track 03: Infrastructure
  Path: /home/user/my-project/.multi-agent/track-03
  Branch: dev-track-03
  HEAD: jkl012 (2 hours ago)
  Status: Pending (0/2 sprints)
  Size: 38 MB

Summary
Total worktrees: 4 (1 main + 3 tracks)
Total disk usage: ~135 MB
Tracks complete: 1/3

Commands:
  Status: /devteam:worktree status
  Cleanup: /devteam:worktree cleanup
  Merge: /devteam:merge-tracks

Read the full file on GitHub · 143 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 · 143 lines · 23 tokens per session scan A 39a7ae5a0d6f

Subscribe to this mod's changes

worktree-list is a skill published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It adds 23 tokens to every session and 993 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.

Related

Other skills, from other repositories

hydra

Multi-agent orchestration framework for Claude Code. Automatically delegates tasks to cheaper, faster sub-agents (Haiku, Sonnet) while maintaining Opus-level quality through verification. Use when working on any coding task — Hydra activates automatically to route file exploration, test running, documentation, code…

AR6420/Hail_Hydra · 83 tokens

quality-stack

Scan a project to detect configured quality and testing tools across JVM (Gradle/Maven), Android (AGP/Compose/KMP), Node.js/TypeScript, and Python ecosystems. Cross-reference against research-backed recommendations and assist with setup. Auto-detects project type(s) including monorepos with mixed ecosystems. Use when…

joaquimscosta/arkhe-claude-plugins · 148 tokens

prototype

Rapid UI prototyping — generates 3 visually distinct HTML/CSS components from a text prompt and serves them in a live browser gallery. Use when user runs /prototype, asks to "prototype a UI", "mock up a component", "generate HTML mockups", "create UI variations", "design exploration", "quick UI concept", or wants to…

joaquimscosta/arkhe-claude-plugins · 118 tokens

lyra

Transform vague inputs into precision-optimized AI prompts for Claude, ChatGPT, Gemini, or other LLMs. Use when user mentions "optimize prompt", "improve prompt", "lyra", "prompt engineering", or needs help crafting effective AI prompts.

joaquimscosta/arkhe-claude-plugins · 56 tokens

taskfile-setup

Install Taskfile (task) and scaffold or audit Taskfile.yml configurations with ecosystem-aware templates. Auto-detects Node.js/pnpm, JVM/Gradle, Python/uv, Docker, and recommends single-file or multi-file (includes) patterns based on project complexity. Use when user runs /devtools:taskfile-setup, mentions "taskfile…

joaquimscosta/arkhe-claude-plugins · 110 tokens

sops-add-key

Add a new machine's age public key to .sops.yaml and re-encrypt all files. Use for multi-machine setups. Use when user mentions "add key", "add machine", "sops add key", "new machine", "authorize machine", "share key", "add public key", "multi machine sops".

joaquimscosta/arkhe-claude-plugins · 72 tokens