worktree-first

A command that starts development in a separate Git worktree. A worktree is an additional working folder connected to the same Git repository, allowing isolated branches.

In plain words
What is it for?
Use it when starting a new development task that should have its own branch and directory.
Why use it?
It keeps changes separated from the current working folder and applies the project’s rules for branching and workspace setup.

Command for Claude Code

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.

agentmods
npx agentmods add commands/kbwen/agentic-os/worktree-first
Clone the repo
git clone --depth 1 https://github.com/KbWen/agentic-os

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 99 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00099
Opus 5 $0.00000 $0.00049
Sonnet 5 $0.00000 $0.00020
Haiku 4.5 $0.00000 $0.00010

Measured 2d ago against content hash 25f46df1d2a2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

worktree-first 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/commands/worktree-first.md · 17 lines

What it actually says

/worktree-first

Execute the canonical workflow: .agent/workflows/worktree-first.md

Required reads before execution

  1. .agentcortex/context/current_state.md — SSoT

Execution

Follow every step in .agent/workflows/worktree-first.md sequentially. The user's task description is: $ARGUMENTS

  • Set up a git worktree-first branching workflow.
  • Follow workspace governance rules strictly.
  • End response with ⚡ ACX.
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. 2d ago First seen · 17 lines · 0 tokens per session scan A 25f46df1d2a2

Subscribe to this mod's changes

worktree-first is a command published in the GitHub repository KbWen/agentic-os (149 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 99 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.