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/christopherlouet/claude-baseWrote 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/christopherlouet/claude-base/git-rename)<a href="https://agentmods.dev/commands/christopherlouet/claude-base/git-rename"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/git-rename/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/christopherlouet/claude-base/git-rename"><img src="https://agentmods.dev/badge/commands/christopherlouet/claude-base/git-rename.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.00000 | $0.00551 |
| Opus 5.5 | $0.00000 | $0.00220 |
| Sonnet 5.5 | $0.00000 | $0.00110 |
| Haiku 4.5 | $0.00000 | $0.00055 |
Grade A, and why
git-rename 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GIT-RENAME Command
Renames the current branch (typically a feature/auto-* branch created by the PreToolUse hook).
Context
$ARGUMENTS
Goal
Give a descriptive name to an auto-generated branch (or simply rename the current branch), locally and on the remote if it has already been pushed.
Usage
/git-rename <new-name>
Examples:
/git-rename feature/git-rename-command
/git-rename fix/login-redirect
/git-rename refactor/api-client
The prefix (feature/, fix/, refactor/...) is optional: if absent, feature/ is added by default.
Workflow
- Check the state
- Read the current branch (
git rev-parse --abbrev-ref HEAD) - Refuse if the branch is
mainormaster(impossible to rename in place without confusion) - Check that the new name is valid (no spaces, no git-special characters)
- Read the current branch (
- Rename locally
git branch -m <new-name>
- Sync the remote (if the branch has been pushed)
- Detect the upstream (
git rev-parse --abbrev-ref --symbolic-full-name @{u}) - If upstream exists:
git push origin :<old-name> <new-name>thengit push origin -u <new-name> - Otherwise: no push, just a message indicating that the branch is local
- Detect the upstream (
- Confirm
- Display the new branch and its remote tracking
Expected output
- Branch renamed locally (and on the remote if applicable)
git status+git branch -vvconfirmation to verify tracking- If a PR already exists on the old branch, warn the user that they must update it manually (GitHub does not follow a branch rename)
Special cases
| Situation | Action |
|---|---|
main/master branch |
REFUSE, explain why |
| New name == current name | Do nothing, informative message |
| New name already exists locally | REFUSE, suggest another name |
| No upstream | Rename locally only |
| PR open on the old branch | Rename + WARN: the PR points to a branch that no longer exists, manual action required |
IMPORTANT: NEVER delete the old remote branch before having pushed the new one (use git push origin :old new in a single command to stay atomic on the remote side).
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.
- 1mo ago First seen · 66 lines · 0 tokens per session scan A 6ecfa107a1ff
git-rename is a command published in the GitHub repository christopherlouet/claude-base (5 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 551 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-09-03.
Other commands, from other repositories
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
deploy
Deploy application with pre/post-deploy checks.
auto-claude
Invoke Auto-Claude autonomous coding framework for complex feature implementation.
cm
Stage working tree changes and create a Conventional Commit (no push).
deps-update
Audit and update dependencies safely.