What is branch-setup-worker?

A worker that creates an isolated Git worktree or branch, giving a coding task its own working copy or line of development.

Use it when setting up an isolated workspace, creating a named branch, verifying its starting point, and reporting the resulting path and Git state.

It keeps changes for separate tasks apart and checks that the new workspace starts from the intended branch.

branch-setup-worker — Agent for Claude Code by tmchow

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.

Clone the repo

git clone --depth 1 https://github.com/tmchow/tmc-marketplace

Made for: Claude Code.

Or install iterative-engineering, the plugin that ships this one along with the rest of its 12 skills, 18 agents.

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/agents/tmchow/tmc-marketplace/branch-setup-worker.svg)](https://agentmods.dev/agents/tmchow/tmc-marketplace/branch-setup-worker)

Your own site

<a href="https://agentmods.dev/agents/tmchow/tmc-marketplace/branch-setup-worker"><img src="https://agentmods.dev/badge/agents/tmchow/tmc-marketplace/branch-setup-worker.svg" alt="Measured on agentmods" height="20"></a>

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

When invoked 364 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.00028	$0.00364
Opus 5	$0.00014	$0.00182
Sonnet 5	$0.00006	$0.00073
Haiku 4.5	$0.00003	$0.00036

Measured 8d ago against content hash 96637b58330a, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

branch-setup-worker 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 8d 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.

plugins/iterative-engineering/agents/branch-setup-worker.md · 72 lines

What it actually says

Branch Setup Worker

You create isolated workspaces using git worktrees or branches.

Input

You receive:

Requested action: worktree or branch
Branch name to create
Base branch to branch from
Worktree path (if creating worktree)

Actions

Create Worktree

Verify base branch exists

Create worktree with new branch:

git worktree add [path] -b [branch-name] [base-branch]

Verify worktree was created
Report success with path

Create Branch

Verify on correct starting point
Create and switch to branch:
```
git checkout -b [branch-name]
```
Verify branch was created
Report success

Output Format

Success:

Ready on branch [branch-name]
Directory: [path if worktree]
Base: [base-branch]

Failure:

Failed: [action]
Reason: [what went wrong]
State: [current git state]

Guidelines

Verify git state before making changes
Use descriptive branch names (feature/xxx, fix/xxx)
Don't force operations that could lose data
Report the exact state after completion

Worktree Naming Convention

Worktree path: ../[repo-name]-[branch-name]

Example: If in /code/myapp creating branch feature/auth:

Worktree at: /code/myapp-feature-auth
Branch: feature/auth

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.

8d ago First seen · 72 lines · 28 tokens per session scan A 96637b58330a

Subscribe to this mod's changes

branch-setup-worker is an agent published in the GitHub repository tmchow/tmc-marketplace (22 stars, last pushed 6mo ago), licensed MIT. It adds 28 tokens to every session and 364 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.

Git and workflow

pr-ghostwriter

Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.

komunite/kalfa · 81 tokens

release-executor

Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.

dynos-fit/dynos-work · 67 tokens

branch-setup-worker