worktree-list

A diagnostic command that lists Git worktrees and their development-track details. Git worktrees are extra working folders that let one repository use multiple branches at the same time.

In plain words
What is it for?
Use it to inspect all worktree paths, branches, commits, and associated development tracks while debugging parallel development.
Why use it?
It helps investigate worktree problems when the normal automated management is not enough. The output connects Git folders and branches with DevTeam track information.

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/michael-harris/devteam/worktree-list
Clone the repo
git clone --depth 1 https://github.com/michael-harris/devteam
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 776 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.00776
Opus 5 $0.00000 $0.00388
Sonnet 5 $0.00000 $0.00155
Haiku 4.5 $0.00000 $0.00078

Measured 2d ago against content hash 43ecc24b772b, 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.

commands/worktree-list.md · 123 lines

How it starts

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

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 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

Alternative: Simple Format

Worktrees:
  main       /home/user/my-project                             (abc123)
  track-01   /home/user/my-project/.multi-agent/track-01       (def456) ✅
  track-02   /home/user/my-project/.multi-agent/track-02       (ghi789) 🔄
  track-03   /home/user/my-project/.multi-agent/track-03       (jkl012) ⏸️

Read the full file on GitHub · 123 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 · 123 lines · 0 tokens per session scan A 43ecc24b772b

Subscribe to this mod's changes

worktree-list is a command published in the GitHub repository michael-harris/devteam (18 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 776 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.