Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/brain-bootstrap/claude-code-brain-bootstrapnpx agentmods add skills/brain-bootstrap/claude-code-brain-bootstrap/worktreeWrote 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/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree)<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree/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.
<a href="https://agentmods.dev/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree"><img src="https://agentmods.dev/badge/skills/brain-bootstrap/claude-code-brain-bootstrap/worktree.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00034 | $0.00406 |
| Opus 5.5 | $0.00014 | $0.00162 |
| Sonnet 5.5 | $0.00007 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
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 1mo 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.
What it actually says
Worktree Skill
Manage git worktrees for parallel, isolated work.
When to use
- Need to review a PR while working on a feature
- Running a long test suite on one branch while developing on another
- Comparing behavior between two branches side-by-side
- Agent team work where each agent operates on a separate branch
Create a worktree
# Create a worktree for an existing branch
git worktree add ../project-feature feature/my-feature
# Create a worktree for a new branch
git worktree add -b feature/new-thing ../project-new-thing main
List active worktrees
git worktree list
Remove a worktree (when done)
# 1. Confirm the work is committed or merged
# 2. Remove the worktree
git worktree remove ../project-feature
# Force remove if needed (work is intentionally discarded)
git worktree remove --force ../project-feature
Prune stale worktree references
git worktree prune
Rules
- NEVER remove a worktree without confirming all work is committed
- Each worktree has its own working directory — changes don't bleed between them
- Worktrees share the same git history — commits on one branch are visible from all
- Name worktrees consistently:
../project-<branch-slug>
For agent team workflows
When spawning multiple subagents for parallel work:
- Create one worktree per agent before spawning
- Give each agent its worktree path as its working directory
- After all agents finish, review each worktree's changes
- Merge or cherry-pick as needed
- Clean up all worktrees after merge
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.
- 1mo ago First seen · 58 lines · 34 tokens per session scan A 81b310454628
worktree is a skill published in the GitHub repository brain-bootstrap/claude-code-brain-bootstrap (11 stars, last pushed 5mo ago), licensed MIT. It adds 34 tokens to every session and 406 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-09-03.
Other skills, from other repositories
review-code
Code review of current git changes with an expert senior-engineer lens. Detects SOLID violations, security risks, and proposes actionable improvements. Use when performing code reviews.
merge-docs
Compare and merge two design docs for the same feature into a single source of truth. Use when you have competing or complementary design/implementation docs (e.g. from separate design runs) that need reconciling into one unified document.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
merge-pr
Merge a pull request with status checks, squash merge, and branch cleanup. Handles worktree contexts.