What is manage-worktrees?

A command for managing Git worktrees across project repositories. A worktree is a separate working folder linked to another branch, allowing multiple branches to be used at once.

Listing active worktrees, creating branch-specific folders, removing individual worktrees, cleaning up merged work, and checking synchronization status.

It helps developers see, create, remove, and clean up parallel branch folders without managing each repository manually.

How bijutharakan/multi-agent-squad configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to bijutharakan/multi-agent-squad. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bijutharakan/multi-agent-squad/main/.claude/commands/manage-worktrees.md

Clone the repo

git clone --depth 1 https://github.com/bijutharakan/multi-agent-squad

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/bijutharakan/multi-agent-squad/manage-worktrees/github.svg)](https://agentmods.dev/commands/bijutharakan/multi-agent-squad/manage-worktrees)

Your own site

<a href="https://agentmods.dev/commands/bijutharakan/multi-agent-squad/manage-worktrees"><img src="https://agentmods.dev/badge/commands/bijutharakan/multi-agent-squad/manage-worktrees/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/bijutharakan/multi-agent-squad/manage-worktrees"><img src="https://agentmods.dev/badge/commands/bijutharakan/multi-agent-squad/manage-worktrees.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 911 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00020	$0.00911
Opus 5.5	$0.00008	$0.00364
Sonnet 5.5	$0.00004	$0.00182
Haiku 4.5	$0.00002	$0.00091

Measured 2mo ago against content hash 2eaa494b3795, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

manage-worktrees 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 2mo 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.

.claude/commands/manage-worktrees.md · 157 lines

How it starts

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

Manage Worktrees Command

Direct control over git worktrees for advanced users and manual interventions.

What This Command Does

List Worktrees - Show all active worktrees
Create Worktree - Manually create for specific repo
Remove Worktree - Clean up specific worktree
Cleanup Merged - Remove all merged worktrees
Sync Status - Update from git state

Usage

/manage-worktrees
"Show me all worktrees"
"Clean up worktrees"
"Remove merged worktrees"

Subcommands

List All Worktrees

/manage-worktrees list

Active Worktrees:
├─ frontend/
│  ├─ feature-auth (3 days old, 12 commits ahead)
│  └─ bugfix-search (1 day old, 2 commits ahead)
├─ backend/
│  ├─ feature-auth (3 days old, 15 commits ahead)
│  └─ feature-payment (new, 3 commits ahead)
└─ mobile/
   └─ feature-auth (2 days old, 8 commits ahead)

Total: 5 active worktrees across 3 repositories

Create New Worktree

/manage-worktrees create

Which repository? backend
Feature name? performance-optimization
Base branch? (default: main) develop

Creating worktree...
✓ Created: worktrees/backend/feature-performance-optimization
✓ Branch: feature/performance-optimization
✓ Based on: origin/develop

Remove Specific Worktree

/manage-worktrees remove

Select worktree to remove:
1. frontend/feature-auth
2. frontend/bugfix-search
3. backend/feature-auth
> 2

Removing frontend/bugfix-search...
✓ Worktree removed
✓ Branch deleted (was merged)

Cleanup All Merged

/manage-worktrees cleanup

Scanning for merged worktrees...
Found 3 merged worktrees:
- frontend/feature-old-ui (merged 5 days ago)
- backend/bugfix-memory-leak (merged 3 days ago)
- mobile/feature-onboarding (merged 1 week ago)

Proceed with cleanup? (y/N) y

✓ Removed 3 merged worktrees
✓ Freed 1.2 GB of disk space

Worktree Information

Each worktree shows:

Repository - Which repo it belongs to
Feature Name - The feature being developed
Age - How long it's been active
Commits - Number ahead of base branch
Status - Clean/Modified/Conflicts
Size - Disk space usage
Last Activity - Last commit time

Read the full file on GitHub · 157 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.

2mo ago First seen · 157 lines · 20 tokens per session scan A 2eaa494b3795

Subscribe to this mod's changes

manage-worktrees is a command published in the GitHub repository bijutharakan/multi-agent-squad (88 stars, last pushed 1y ago), licensed MIT. It adds 20 tokens to every session and 911 once invoked, about $0.0001 per session on Opus 5.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.

Git and workflow

manage-worktrees next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
manage-worktreesbijutharakan/multi-agent-squad	Command	88	1y ago	MIT	A	20	Claude Code
merge-conflict-analysisrjmurillo/ai-agents	Command	49	yesterday	MIT	A	0	GitHub Copilot
release-notesOpenHands/extensions	Command	176	yesterday	MIT	A	44	Claude Code
commitechoVic/blade-code	Command	181	24d ago	MIT	A	8	Claude Code
repo-audittractorjuice/arc-kit	Command	2.3k	2d ago	none	A	29	Claude Code
propsmill/infrahub-mcp	Command	10	yesterday	Apache-2.0	A	18	Claude Code
codex-reviewoalders/kitchen-sink	Command	5	3d ago	MIT	A	41	Claude Code

multi-agent-squad: Command for Claude Code