agentmods.dev

git-worktree

git-worktree is a skill for Claude Code from tlangridge/agent-swarm. It costs 31 tokens per session (498 once invoked), scanned A, original, MIT.

A Git workflow for working in isolated copies of a project, called worktrees, with separate branches for each task.

In plain words
What is it for?
It helps agents create task branches, commit changes, push them, and open pull requests for review without switching away from their assigned worktree.
Why use it?
It reduces merge conflicts when multiple agents work on the same codebase and connects branches to their assigned tasks.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter.

not rated 5repo 8mo ago A scan 31 tokens original MIT

Good fit It helps agents create task branches, commit changes, push them, and open pull requests for review without switching away from their assigned worktree.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/tlangridge/agent-swarm/git-worktree
View source ↗ tlangridge/agent-swarm
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.

Any agent
npx skills add tlangridge/agent-swarm --skill git-worktree
Clone the repo
git clone --depth 1 https://github.com/tlangridge/agent-swarm

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.

agentmods badge for git-worktree

README.md
[![agentmods](https://agentmods.dev/badge/skills/tlangridge/agent-swarm/git-worktree/github.svg)](https://agentmods.dev/skills/tlangridge/agent-swarm/git-worktree)
Your own site
<a href="https://agentmods.dev/skills/tlangridge/agent-swarm/git-worktree"><img src="https://agentmods.dev/badge/skills/tlangridge/agent-swarm/git-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.

agentmods 80×15 button for git-worktree

Your own site · 80×15
<a href="https://agentmods.dev/skills/tlangridge/agent-swarm/git-worktree"><img src="https://agentmods.dev/badge/skills/tlangridge/agent-swarm/git-worktree.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 31 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 498 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00031 $0.00498
Opus 5.5 $0.00012 $0.00199
Sonnet 5.5 $0.00006 $0.00100
Haiku 4.5 $0.00003 $0.00050

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

Security

Grade A, and why

git-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 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.

skills/git-worktree/SKILL.md · 67 lines

What it actually says

Git Worktree Isolation

Each agent works in a dedicated git worktree with its own branch. This prevents merge conflicts between agents working simultaneously.

Branch Convention

Your worktree branch follows the pattern: swarm/<agent-name>/<date>

For example: swarm/alice/20260304

Critical Rules

  1. Do NOT switch branches. Your worktree is checked out to your assigned branch. Switching branches would break isolation. If you need to reference another branch, use git diff or git log with the branch name -- do not checkout.

  2. Do NOT run git checkout on any branch other than your assigned one. The worktree system manages branches for you.

  3. Commit frequently. Since you are on your own branch, there is no risk of conflicting with others. Commit early, commit often.

Linking Branches to Tasks

When you start working on a task, link your branch:

swarm task update <id> --branch <your-branch>

This makes it visible in the dashboard which task is associated with which branch.

Creating Pull Requests

When your task is complete:

  1. Commit and push your branch
  2. Create a PR targeting the main branch
  3. Link the PR to your task: 
    swarm task update <id> --pr <number> --pr-url <url>
  4. If working on a GitHub issue, link that too: 
    swarm task update <id> --issue <number> --issue-url <url>

Working with Other Agents' Branches

If you need to see what another agent has done:

git log swarm/<other-agent>/<date> --oneline -10
git diff main..swarm/<other-agent>/<date> -- <file>

Do NOT merge other agents' branches into yours unless explicitly instructed by the lead.

Handling Merge Conflicts

If your branch falls behind main and you need updates:

git fetch origin
git merge origin/main

Resolve any conflicts in your worktree. If conflicts are complex, notify the lead via swarm msg.

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.

  1. 2mo ago First seen · 67 lines · 31 tokens per session scan A 92e676e2fd40

Subscribe to this mod's changes

git-worktree is a skill published in the GitHub repository tlangridge/agent-swarm (5 stars, last pushed 8mo ago), licensed MIT. It adds 31 tokens to every session and 498 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-31.

Git and workflow
Related

git-worktree compared with skills from other repositories

git-worktree next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
git-worktreetlangridge/agent-swarmSkill58mo agoMITA31Claude Code
merge-batchdiegosouzapw/OmniRouteSkill85ktodayMITA46Claude Code
prowler-commitprowler-cloud/prowlerSkill15kyesterdayApache-2.0A44Claude Code, Codex
gh-auth-isolationgithub/gh-awSkill5.6ktodayMITA20Claude Code, Codex
comet-githubrpamis/cometSkill3.3ktodayMITA72Claude Code, Codex
github-skillzeenie-ai/OpenCompanySkill1.1k3d agoMITA51Claude Code
re0-mergeLilMGenius/paperthinSkill1.4ktodayMITA70Claude Code