Borrowing it
Nothing to install: this file belongs to dixus/claudeframework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dixus/claudeframework/main/.claude/commands/rebase-master.mdgit clone --depth 1 https://github.com/dixus/claudeframeworkWrote 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/dixus/claudeframework/rebase-master)<a href="https://agentmods.dev/commands/dixus/claudeframework/rebase-master"><img src="https://agentmods.dev/badge/commands/dixus/claudeframework/rebase-master/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/dixus/claudeframework/rebase-master"><img src="https://agentmods.dev/badge/commands/dixus/claudeframework/rebase-master.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.00011 | $0.00220 |
| Opus 5.5 | $0.00004 | $0.00088 |
| Sonnet 5.5 | $0.00002 | $0.00044 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
rebase-master 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 2mo 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
Rebase the current branch onto the latest origin/master:
- Run
git fetch origin masterto get the latest master. - Check for uncommitted changes with
git status --short. If there are any, stash them withgit stash push -m "auto-stash before rebase". - Run
git rebase origin/master. - If there are merge conflicts:
- Show the conflicted files.
- For each conflict, read the file, resolve it by keeping both sides where sensible (prefer master for infrastructure, prefer branch for feature code), then
git addthe resolved file. - Run
git rebase --continue. Repeat until done.
- If changes were stashed in step 2, run
git stash popto restore them. - Run
git push --forceto update the remote branch with the rebased history. - Show
git log --oneline -5to confirm the result.
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.
- 2mo ago First seen · 17 lines · 11 tokens per session scan A 88117b2cbce6
rebase-master is a command published in the GitHub repository dixus/claudeframework (10 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 220 once invoked, about $0.0000 per session on Opus 5.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.
Other commands, from other repositories
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.
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.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
release-plan
A release-planning command for a software change. It documents the release scope, rollback plan, gradual or full rollout, and monitoring before waiting for human approval.