create-branch

A command that creates a Git branch and a linked worktree using a project naming pattern. A Git worktree is a separate directory connected to the same repository, allowing another branch to be worked on independently.

In plain words
What is it for?
Use it to start feature, fix, documentation, refactoring, test, or maintenance work with a named branch, sibling worktree, and shared environment file.
Why use it?
It standardizes branch names and sets up a separate working directory without requiring each setup step by hand.

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/kayba-ai/agentic-context-engine/create-branch
Clone the repo
git clone --depth 1 https://github.com/kayba-ai/agentic-context-engine

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 490 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.00490
Opus 5 $0.00000 $0.00245
Sonnet 5 $0.00000 $0.00098
Haiku 4.5 $0.00000 $0.00049

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

Security

Grade A, and why

create-branch 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 3d 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.

.claude/commands/create-branch.md · 40 lines

What it actually says

Create a new git branch with an associated worktree following the project naming convention.

Format: <type>/<developer>/<description> Worktree: ../<sanitized-branch-name> (sibling to current worktree)

Arguments: $ARGUMENTS should be in format: <type> <description>

Examples:

  • /create-branch feature add-caching → branch: feature/<dev>/add-caching, worktree: ../feature-<dev>-add-caching
  • /create-branch fix login-error → branch: fix/<dev>/login-error, worktree: ../fix-<dev>-login-error

Steps:

  1. Parse type and description from arguments (validate type is one of: feature, fix, docs, refactor, test, chore)
  2. Get developer name from git config user.name (sanitize: lowercase, replace spaces with hyphens)
  3. Construct branch name: <type>/<developer>/<description>
  4. Construct worktree path: ../<type>-<developer>-<description> (replace all / with -)
  5. Create branch and worktree atomically: git worktree add -b <branch> <worktree-path>
  6. Symlink .env from the main worktree into the new worktree:
    • Get the main worktree path: git worktree list --porcelain | head -1 (first worktree line)
    • If <main-worktree>/.env exists, create symlink: ln -s <main-worktree>/.env <new-worktree>/.env
    • If .env doesn't exist in main worktree, skip silently
  7. Report success with the created branch name and worktree path

Valid types: feature, fix, docs, refactor, test, chore

On success, output:

✓ Created branch: <branch-name>
✓ Created worktree: <worktree-path>
✓ Linked .env → <main-worktree>/.env

To switch to the new worktree:
  cd <worktree-path>

Error handling:

  • If type is invalid, show valid types and abort
  • If branch already exists, suggest checking it out instead
  • If worktree path exists, suggest using existing worktree
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. 3d ago First seen · 40 lines · 0 tokens per session scan A 0921e0255595

Subscribe to this mod's changes

create-branch is a command published in the GitHub repository kayba-ai/agentic-context-engine (2,561 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 490 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.