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.
git clone --depth 1 https://github.com/danielraffel/generous-corp-marketplaceWrote 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.
[](https://agentmods.dev/commands/danielraffel/generous-corp-marketplace/rename-branch)<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.
<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>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.00006 | $0.00454 |
| Opus 5 | $0.00003 | $0.00227 |
| Sonnet 5 | $0.00001 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00045 |
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.
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:
-
Parse arguments:
- Extract worktree path (required)
- Extract old branch name (required)
- Extract new branch name (required)
-
Validation:
- Verify all three arguments are provided
- Check that old and new names are different
-
Call MCP tool:
- Use
mcp__worktree__worktree_rename_branch - Pass
worktree_path,old_name,new_name
- Use
-
Display results:
- Show the rename operation:
- Renaming branch in:
- From:
- To:
- ✅ Branch renamed successfully
- Show the rename operation:
-
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
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.
- 11d ago First seen · 68 lines · 6 tokens per session scan A 457b17cb3ddc
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.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.