Borrowing it
Nothing to install: this file belongs to DIGI-UW/OpenELIS-Global-2. 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/DIGI-UW/OpenELIS-Global-2/develop/.specify/oe/commands/careful-rebase.mdgit clone --depth 1 https://github.com/DIGI-UW/OpenELIS-Global-2Wrote 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/digi-uw/openelis-global-2/careful-rebase)<a href="https://agentmods.dev/commands/digi-uw/openelis-global-2/careful-rebase"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/careful-rebase/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/digi-uw/openelis-global-2/careful-rebase"><img src="https://agentmods.dev/badge/commands/digi-uw/openelis-global-2/careful-rebase.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.04101 |
| Opus 5 | $0.00000 | $0.02050 |
| Sonnet 5 | $0.00000 | $0.00820 |
| Haiku 4.5 | $0.00000 | $0.00410 |
Grade A, and why
careful-rebase 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 12d 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 — 438 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Careful Rebase Workflow
When the user invokes /careful-rebase (optionally with arguments), perform a
careful, checkpointed rebase workflow with:
- A backup branch created up-front
- A rebase plan (what will move, onto what) with a projected change summary
- A conflict risk report (where conflicts are likely) including base-only improvements
- An answer session to resolve ambiguities before/while resolving conflicts (only if needed)
- An optional squash-before-rebase step
- A no-loss audit that compares pre/post rebase branch deltas and i18n key sets
- Validation and a post-rebase report (including
git range-diff)
This command is intentionally conservative: it should plan first, then require explicit user confirmation before any history-rewriting actions.
Review Cycle (required gates)
This workflow must have a clear, repeatable review cycle:
- Pre-rebase confirmation (REQUIRED): show the projected changes (commits to replay, diffstat, hotspots, base-only improvements, and whether a force-push will be needed) and stop until the user explicitly says “Proceed with rebase”.
- QA session checkpoint (REQUIRED): after the rebase, produce a short QA checklist and stop until the user explicitly confirms “QA approved” before suggesting any force-push.
User Input
$ARGUMENTS
Interpret arguments best-effort. Support these patterns:
/careful-rebase→ default base branch:developif present, elsemain/careful-rebase <base>→ base branch/ref (e.g.,develop,origin/develop)- Optional flags (if present in user input):
--squash→ squash the branch to one commit before rebasing--no-squash→ do not squash (default)--preserve-merges→ usegit rebase --rebase-merges--validate {quick|standard|thorough}→ pick validation depth
If any inputs are unclear, ask a single concise question and continue with safe defaults.
Safety Rules (non-negotiable)
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.
- 12d ago First seen · 438 lines · 0 tokens per session scan A ca3d2f1362d0
careful-rebase is a command published in the GitHub repository DIGI-UW/OpenELIS-Global-2 (252 stars, last pushed today), licensed MPL-2.0. It costs nothing until one of its globs matches a file; then it loads 4,101 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-08-30.
Other commands, from other repositories
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
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.
commit-claude-config
Version the Solana AI Kit config in git (un-ignores .claude/, CLAUDE.md, .mcp.json, .gitmodules and commits them).
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.
feat
Quick feature commit. Use for new feature, add feature, implement, create new.
step6-ship
Pipeline Step 6 — Ship the completed phase: commit, update roadmap, capture postmortem, optionally push and create PR.