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/michael-harris/devteam/worktree-cleanupgit 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.00000 | $0.01361 |
| Opus 5 | $0.00000 | $0.00681 |
| Sonnet 5 | $0.00000 | $0.00272 |
| Haiku 4.5 | $0.00000 | $0.00136 |
Grade A, and why
worktree-cleanup 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Cleanup Command
Debug/Expert Command - Manually clean up development track worktrees.
Note: This command is rarely needed. Worktrees are cleaned up automatically after
/devteam:implementmerges all tracks. Use this only if automatic cleanup failed or you need manual control.
Command Usage
/devteam:worktree cleanup # Clean up all worktrees
/devteam:worktree cleanup 01 # Clean up specific track
/devteam:worktree cleanup --all # Clean up worktrees AND delete branches
Warning
This command is destructive. Use with caution.
Your Process
Step 1: Load State and Validate
- Load state from SQLite database (
.devteam/devteam.db) viasource scripts/state.sh - Verify worktree mode enabled
- If specific track, verify track exists
- Check if tracks are complete (warning if not)
Step 2: Safety Checks
For each worktree to be removed:
cd "$worktree_path"
# Check for uncommitted changes
if [ -n "$(git status --porcelain)" ]; then
echo "❌ ERROR: Uncommitted changes in $worktree_path"
echo " Please commit or stash changes first"
exit 1
fi
# Check if pushed to remote
if git status | grep "Your branch is ahead"; then
echo "⚠️ WARNING: Unpushed commits in $worktree_path"
echo " Recommend pushing before cleanup"
read -p "Continue anyway? (y/N): " confirm
if [ "$confirm" != "y" ]; then
exit 1
fi
fi
Step 3: Remove Worktrees
For each worktree:
cd "$MAIN_REPO"
echo "Removing worktree: $worktree_path"
git worktree remove "$worktree_path"
if [ $? -eq 0 ]; then
echo "✓ Removed: $worktree_path"
else
echo "❌ Failed to remove: $worktree_path"
echo " Try: git worktree remove --force $worktree_path"
fi
Step 4: Remove Empty Directory
if [ -d ".multi-agent" ] && [ -z "$(ls -A .multi-agent)" ]; then
rmdir .multi-agent
echo "✓ Removed empty .multi-agent/ directory"
fi
Step 5: Optionally Delete Branches
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 · 209 lines · 0 tokens per session scan A 23c5366dd4a8
worktree-cleanup 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,361 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.
Other commands, from other repositories
stats
Show real token usage, delegation rate, and actual savings for the current Hydra session (parses Claude Code session JSONL — no AI estimation).
map
View, rebuild, or query the codebase dependency map.
debug
Systematic debugging with automated investigation and 4-phase methodology. Default: inline evidence gathering and diagnosis. --deep: spawns systematic-debugger agent for full autonomous debugging. Use for errors, stack traces, test failures, or unexpected behavior.
double-check
Comprehensive verification with automated quality gates, confession gathering, and confidence-based issue filtering. Default: self-review with gates. --deep: multi-agent review via code-reviewer agent. Use before committing, after fixing bugs, or to validate feature completeness.
code-explain
Explain complex code through clear narratives and visual diagrams.
health
Run documentation health checks (freshness, links, drift, cross-doc consistency).