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/sigistry/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/sigistry/marketplace/rebase-plan)<a href="https://agentmods.dev/commands/sigistry/marketplace/rebase-plan"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/rebase-plan/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/sigistry/marketplace/rebase-plan"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/rebase-plan.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.00021 | $0.00810 |
| Opus 5 | $0.00010 | $0.00405 |
| Sonnet 5 | $0.00004 | $0.00162 |
| Haiku 4.5 | $0.00002 | $0.00081 |
Grade A, and why
rebase-plan 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 5d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyze the commits on the current branch and produce a concrete git rebase -i plan that yields a clean, reviewable history, with a plain-English rationale for every pick/reword/squash/fixup/drop and an explicit risk assessment. This command PLANS ONLY; it never runs the rebase. $ARGUMENTS optionally names the base branch.
Process
Step 1: Resolve the base and the commit range
- Base =
$ARGUMENTSif given, else the auto-detected default (origin/HEAD, thenmain/master/develop). - Range =
git merge-base HEAD <base>..HEAD. Everything below operates on commits in this range only.
Step 2: Inventory the commits
git log --oneline --stat <merge-base>..HEAD: commits, messages, and files touched.git log --format='%H %ci %an %s' <merge-base>..HEAD: dates and authors.- Note merge commits (
git log --merges <merge-base>..HEAD), interactive rebase will linearize them; flag this.
Step 3: Assess what has already been shared
git rev-parse --abbrev-ref --symbolic-full-name @{upstream}andgit log --oneline @{upstream}..HEAD: which commits are already pushed.- Any commit at or below the upstream tip has likely been seen by others. Rewriting it requires a force-push and can disrupt collaborators. Mark these clearly.
Step 4: Propose the rebase todo
Classify each commit and build the todo list:
| Action | Use when |
|---|---|
pick |
The commit is good as-is |
reword |
Good change, weak/incorrect message |
squash |
Merge into the previous commit, combine messages |
fixup |
Merge into the previous commit, discard this message (typo/wip follow-ups) |
drop |
Debug prints, reverted experiments, accidental commits |
edit |
The commit needs to be split or amended mid-rebase |
Group fixups directly under the commit they belong to. Aim for a history where each surviving commit is one logical, buildable, reviewable change.
Step 5: Output the plan
Provide two things:
- The exact
git rebase -itodo content, in order, that the user pastes into the editor:
pick a1b2c3d feat(api): add pagination
fixup e4f5g6h wip
reword h7i8j9k fix typo
drop k0l1m2n debug logging
- A numbered rationale, one line per changed action explaining why.
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.
- 5d ago First seen · 62 lines · 21 tokens per session scan A c5ed57710a41
rebase-plan is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed 4d ago), licensed MIT. It adds 21 tokens to every session and 810 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
commit
Create well-formatted commits with conventional commit messages and emojis.
version-bump
Bump versions across the monorepo during release process.
release
Generate changelog, bump version, and create git tag.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
release
Prepare a release of the sonu plugin — decide the semver bump, sync the version and plugin description across all five homes, run /validate, then hand to /sonu:ship. Only meaningful inside the claude-plugins repo; in any other repo, say so and stop.
cancel-ship
Cancel active ship pipeline.