worktree-status

A debugging command that reports the state of development worktrees. A Git worktree is a separate working folder linked to the same repository, often used to work on several branches at once.

In plain words
What is it for?
Use it to see worktree paths, branches, changes, and related status for all tracks or one selected track.
Why use it?
It removes the need to inspect each worktree and branch manually when checking parallel development tracks.

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-status
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 1,553 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.01553
Opus 5 $0.00000 $0.00776
Sonnet 5 $0.00000 $0.00311
Haiku 4.5 $0.00000 $0.00155

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

commands/worktree-status.md · 239 lines

How it starts

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

Worktree Status Command

Debug/Expert Command - Shows detailed status of all development track worktrees.

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

Command Usage

/devteam:worktree status         # Show all worktree status
/devteam:worktree status 01      # Show status for specific track

Your Process

Step 1: Load State from SQLite

Query the SQLite database (.devteam/devteam.db) to get worktree configuration:

source scripts/state.sh

# Check worktree mode
mode=$(get_state "parallel_tracks.mode")

If not worktree mode:

This project is not using git worktrees (mode: state-only)

No worktrees to show status for.

Step 2: Collect Worktree Information

For each track in the state database:

track_num = "01"
worktree_path = ".multi-agent/track-01"
branch_name = "dev-track-01"

# Check if worktree exists
if [ -d "$worktree_path" ]; then
    exists = true

    cd "$worktree_path"

    # Get git status
    current_branch = $(git rev-parse --abbrev-ref HEAD)
    uncommitted = $(git status --porcelain | wc -l)
    ahead = $(git rev-list --count @{u}..HEAD 2>/dev/null || echo "N/A")
    behind = $(git rev-list --count HEAD..@{u} 2>/dev/null || echo "N/A")

    # Get sprint status from SQLite database
    sprints = get_sprints_for_track(track_num)  # via: source scripts/state.sh
    completed_sprints = count(s for s in sprints if s.status == "completed")
    total_sprints = len(sprints)

    # Get task status from SQLite database
    tasks = get_tasks_for_track(track_num)  # via: source scripts/state.sh
    completed_tasks = count(t for t in tasks if t.status == "completed")
    total_tasks = len(tasks)

else
    exists = false
fi

Step 3: Display Status

For all tracks:

═══════════════════════════════════════════
 Development Track Status
═══════════════════════════════════════════

Mode: Git worktrees (physical isolation)
Base path: .multi-agent/

Track 1: Backend API
───────────────────────────────────────────
Status: ✅ ACTIVE
Location: .multi-agent/track-01/
Branch: dev-track-01 (current)
Progress: 2/2 sprints complete (7/7 tasks)
Git status:
  Uncommitted changes: 0
  Ahead of remote: 3 commits
  Behind remote: 0
  Action: ⚠️  Push recommended

Track 2: Frontend
───────────────────────────────────────────
Status: 🔄 IN PROGRESS
Location: .multi-agent/track-02/
Branch: dev-track-02 (current)
Progress: 1/2 sprints complete (4/6 tasks)
Git status:
  Uncommitted changes: 5 files
  Ahead of remote: 2 commits
  Behind remote: 0
  Action: ⚠️  Commit and push needed

Track 3: Infrastructure
───────────────────────────────────────────
Status: ⏸️  PENDING
Location: .multi-agent/track-03/
Branch: dev-track-03 (current)
Progress: 0/2 sprints complete (0/5 tasks)
Git status:
  Uncommitted changes: 0
  Ahead of remote: 0
  Behind remote: 0
  Action: ✓ Clean

═══════════════════════════════════════════
Summary
═══════════════════════════════════════════
Total tracks: 3
Complete: 1
In progress: 1
Pending: 1

Warnings:
⚠️  Track 1: Unpushed commits (backup recommended)
⚠️  Track 2: Uncommitted changes (commit before merge)

Next steps:
  Track 2: /devteam:implement --sprint all 02
  Track 3: /devteam:implement --sprint all 03
  After all complete: /devteam:merge-tracks

Read the full file on GitHub · 239 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 · 239 lines · 0 tokens per session scan A 591078fee38b

Subscribe to this mod's changes

worktree-status 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 1,553 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.