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 commands/bijutharakan/multi-agent-squad/manage-worktreesgit clone --depth 1 https://github.com/bijutharakan/multi-agent-squadWrote 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.
[](https://agentmods.dev/commands/bijutharakan/multi-agent-squad/manage-worktrees)<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="Measured on agentmods" height="20"></a>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.00020 | $0.00911 |
| Opus 5 | $0.00010 | $0.00456 |
| Sonnet 5 | $0.00004 | $0.00182 |
| Haiku 4.5 | $0.00002 | $0.00091 |
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 5d 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 — 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
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.
- 5d ago First seen · 157 lines · 20 tokens per session scan A 2eaa494b3795
manage-worktrees is a command published in the GitHub repository bijutharakan/multi-agent-squad (86 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. 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.