A Git worktree dashboard for the current repository. A worktree is a separate working directory connected to the same Git repository, useful for handling branches in parallel.

Listing worktrees, branches, dirty-file counts, locks, assigned agents, recent activity, sizes, storage details, and commands for creating or managing worktrees.

It shows where repository worktrees are, which ones are changed or missing, and what work is active.

worktree — Command by agallardol

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/agallardol/zcode-git-worktrees/worktree

Clone the repo

git clone --depth 1 https://github.com/agallardol/zcode-git-worktrees

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 337 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.

Model	Per session	Once invoked
Fable 5	$0.00013	$0.00337
Opus 5	$0.00006	$0.00169
Sonnet 5	$0.00003	$0.00067
Haiku 4.5	$0.00001	$0.00034

Measured yesterday against content hash 6b1c698b4fbb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

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.

plugins/git-worktrees/commands/worktree.md · 17 lines

What it actually says

Show the git worktree dashboard for the current repository.

Call the mcp__git-worktrees__worktrees_list tool (no arguments needed — it operates on the current directory).
Render the result as a compact markdown table with columns: Name, Branch, Status (dirty count, locked, agent, MISSING), Last activity, Size. Highlight the row for the worktree the session is currently inside, if any (compare the session's working directory against each path).
Below the table, print the store location and free disk space, then these hints:
- /worktree:new <name> [task description] — create a worktree (auto-named if omitted; spawns a background agent when a task is given)
- /worktree:status <name> · /worktree:remove <name> · /worktree:cleanup · /worktree:pr <number>
- /worktree:end [name] — commit everything and remove the worktree (end-of-task)
- /worktree:auto — per-session automatic worktrees (on by default; off disables, per-repo override in .zcode/worktree.json)
If worktrees is empty, say so in one friendly line and suggest /worktree:new <name> with a one-sentence explanation of what worktrees are good for (parallel isolated tasks on one repo).

Do not run raw git commands for this — the tool output is complete.

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.

yesterday First seen · 17 lines · 13 tokens per session scan A 6b1c698b4fbb

Subscribe to this mod's changes

worktree is a command published in the GitHub repository agallardol/zcode-git-worktrees (1 stars, last pushed 11d ago), licensed MIT. It adds 13 tokens to every session and 337 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-31.

Analytics and metrics Git and workflow developer-tools git-worktrees mcp worktree zcode

worktree

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other commands, from other repositories

check

init

opsx-bulk-apply

setup

update

push