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.
npx agentmods add skills/michael-harris/devteam/worktree-statusnpx skills add michael-harris/devteam --skill worktree-statusgit clone --depth 1 https://github.com/michael-harris/devteamWhat 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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00023 | $0.01708 |
| Opus 5 | $0.00012 | $0.00854 |
| Sonnet 5 | $0.00005 | $0.00342 |
| Haiku 4.5 | $0.00002 | $0.00171 |
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.
How it starts
The opening of the file, as written. The whole thing — 247 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"
Worktree mode: !source "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh" && get_kv_state "parallel_tracks.mode" 2>/dev/null || echo "unknown"
Native worktrees: !ls -d .claude/worktrees/*/ 2>/dev/null || echo "None"
Legacy worktrees: !ls -d .multi-agent/track-*/ 2>/dev/null || echo "None"
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 "${CLAUDE_PLUGIN_ROOT}/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 "${CLAUDE_PLUGIN_ROOT}/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 "${CLAUDE_PLUGIN_ROOT}/scripts/state.sh"
completed_tasks = count(t for t in tasks if t.status == "completed")
total_tasks = len(tasks)
else
exists = false
fi
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.
- 2d ago First seen · 247 lines · 23 tokens per session scan A bfaf3d7191f3
worktree-status 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 1,708 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.
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…
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…
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.
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…
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".
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…