rename-branch

rename-branch is a command for Claude Code from danielraffel/generous-corp-marketplace. It costs 6 tokens per session (454 once invoked), scanned A, original, MIT.

A command for renaming a Git branch inside a specified worktree, a separate working directory connected to the same repository.

In plain words
What is it for?
Use it by providing a worktree path, the current branch name, and the new branch name.
Why use it?
It checks the required paths and branch names before changing the branch name, helping avoid common rename mistakes.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the worktree-manager plugin — 8 commands shipped together

Good fit Use it by providing a worktree path, the current branch name, and the new branch name.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/danielraffel/generous-corp-marketplace/rename-branch
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/danielraffel/generous-corp-marketplace

Made for: Claude Code.

Or install worktree-manager, the plugin that ships this one along with the rest of its 8 commands.

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

README.md
[![agentmods](https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/rename-branch/github.svg)](https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/rename-branch)
Your own site
<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/rename-branch"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/rename-branch/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 rename-branch

Your own site · 80×15
<a href="https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/rename-branch"><img src="https://agentmods.dev/badge/commands/danielraffel/generous-corp-marketplace/rename-branch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 454 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.00006 $0.00454
Opus 5 $0.00003 $0.00227
Sonnet 5 $0.00001 $0.00091
Haiku 4.5 $0.00001 $0.00045

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

Security

Grade A, and why

rename-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 11d 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/worktree-manager/commands/rename-branch.md · 68 lines

What it actually says

Worktree Rename Branch Command

Rename a git branch within a specific worktree.

Usage

/worktree-manager:rename-branch <worktree-path> <old-name> <new-name>

Instructions for Claude

When user invokes this command:

  1. Parse arguments:

    • Extract worktree path (required)
    • Extract old branch name (required)
    • Extract new branch name (required)
  2. Validation:

    • Verify all three arguments are provided
    • Check that old and new names are different
  3. Call MCP tool:

    • Use mcp__worktree__worktree_rename_branch
    • Pass worktree_path, old_name, new_name
  4. Display results:

    • Show the rename operation:
      • Renaming branch in:
      • From:
      • To:
      • ✅ Branch renamed successfully
  5. Error handling:

    • Old branch doesn't exist → suggest checking branch name with git branch
    • New branch already exists → suggest different name or delete existing
    • Not on the branch → may need to switch to it first

Examples

Basic rename:

User: /worktree-manager:rename-branch ~/worktrees/feature-x old-name new-name
Claude: ✅ Branch renamed from 'old-name' to 'new-name'
        Git references have been updated automatically

Rename current branch:

User: /worktree-manager:rename-branch ~/worktrees/my-feature feature/old feature/new
Claude: [Renames the branch in the specified worktree]

Notes

  • Renaming updates all git references automatically
  • The worktree continues to work normally after rename
  • This only renames the local branch, not remote branches
  • To update remote, use: git push origin :old-name new-name
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. 11d ago First seen · 68 lines · 6 tokens per session scan A 457b17cb3ddc

Subscribe to this mod's changes

rename-branch is a command published in the GitHub repository danielraffel/generous-corp-marketplace (11 stars, last pushed 12d ago), licensed MIT. It adds 6 tokens to every session and 454 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-30.