new-branch

new-branch is a command for Claude Code from bravew/trove. It costs 8 tokens per session (479 once invoked), scanned A, original, MIT.

A command that creates a new Git branch, which is a separate line of development, from a plain-language request.

In plain words
What is it for?
Use it before starting a feature, bug fix, maintenance task, documentation change, refactor, test, or performance improvement.
Why use it?
It removes the need to choose a branch prefix and name by hand while checking whether the name is already taken.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

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/bravew/trove/new-branch
Clone the repo
git clone --depth 1 https://github.com/bravew/trove

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 new-branch

README.md
[![agentmods](https://agentmods.dev/badge/commands/bravew/trove/new-branch.svg)](https://agentmods.dev/commands/bravew/trove/new-branch)
Your own site
<a href="https://agentmods.dev/commands/bravew/trove/new-branch"><img src="https://agentmods.dev/badge/commands/bravew/trove/new-branch.svg" alt="Measured on agentmods" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 479 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.1 $0.00008 $0.00479
Opus 5 $0.00004 $0.00239
Sonnet 5 $0.00002 $0.00096
Haiku 4.5 $0.00001 $0.00048

Measured 6d ago against content hash cdc31f6d2c0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

new-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 6d 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.

commands/new-branch.md · 73 lines

What it actually says

Create Git Branch

Generate a conventional branch name based on user request and create a new git branch.

Variables

User request: $ARGUMENTS

Instructions

Step 1: Check Current Branch

  • Check current branch: git branch --show-current
  • Warn (but proceed) if not on a standard base branch (staging, production, main, master, develop)

Step 2: Generate Branch Name

Prefixes:

  • feat/ - New feature or enhancement
  • fix/ - Bug fix
  • chore/ - Maintenance tasks (dependencies, configs, etc.)
  • docs/ - Documentation only changes
  • refactor/ - Code refactoring (no functionality change)
  • test/ - Adding or updating tests
  • perf/ - Performance improvements

Naming Rules:

  • Use kebab-case (lowercase with hyphens)
  • Be descriptive but concise (max 50 characters)
  • No special characters except hyphens, no spaces

Examples:

  • "Add user settings page" → feat/add-user-settings
  • "Fix SSE stream disconnect" → fix/sse-stream-disconnect
  • "Update README documentation" → docs/update-readme
  • "Refactor state management" → refactor/state-management

Step 3: Check Branch Exists

If the branch name already exists, append -v2, -v3, etc. until unique:

if git show-ref --verify --quiet refs/heads/<branch-name>; then
  COUNTER=2
  while git show-ref --verify --quiet refs/heads/<branch-name>-v$COUNTER; do
    COUNTER=$((COUNTER + 1))
  done
  BRANCH_NAME="<branch-name>-v$COUNTER"
fi

Step 4: Create and Checkout Branch

git checkout -b <branch-name>
git branch --show-current

Important: Branch is created locally only — push happens later via the pr or ship command.

Report

Output the branch name and confirm checkout.

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. 6d ago First seen · 73 lines · 8 tokens per session scan A cdc31f6d2c0f

Subscribe to this mod's changes

new-branch is a command published in the GitHub repository bravew/trove (10 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 479 once invoked, about $0.0000 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-31.