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.
npx agentmods add commands/hg-pyun/claude-code-marketplace/git-rebase-stackgit clone --depth 1 https://github.com/hg-pyun/claude-code-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/hg-pyun/claude-code-marketplace/git-rebase-stack)<a href="https://agentmods.dev/commands/hg-pyun/claude-code-marketplace/git-rebase-stack"><img src="https://agentmods.dev/badge/commands/hg-pyun/claude-code-marketplace/git-rebase-stack.svg" alt="Measured on agentmods" 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 | $0.00151 | $0.02567 |
| Opus 5 | $0.00076 | $0.01283 |
| Sonnet 5 | $0.00030 | $0.00513 |
| Haiku 4.5 | $0.00015 | $0.00257 |
Grade A, and why
git-rebase-stack 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 3d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<Use_When>
- The base of a stacked-PR chain has changed and intermediate branches need updating
- A middle PR in the stack merged (or was dropped) and the rest of the stack needs to rebase onto the new tip
- The user wants the entire stack synced to the current default branch
- The user invokes
/git-rebase-stackwith optional natural-language intent </Use_When>
<Do_Not_Use_When>
- Single-branch rebase (no stack) — use
git rebasedirectly - Interactive rebase or fixup of a single branch
- The user wants to change a GitHub PR's base branch (out of scope)
- The user wants automatic test execution after rebase (out of scope) </Do_Not_Use_When>
<Why_This_Exists>
Stacked PRs are powerful but error-prone to maintain by hand. --update-refs (introduced in git 2.38) updates intermediate branch refs in a single rebase, but only if the invoker knows the right <old-base> for --onto. This command auto-detects the stack topology from git log --graph + branch reflogs, picks the right invocation, and offers backup branches when the stack is complex enough that recovery via git reflog alone would be painful.
</Why_This_Exists>
<Execution_Policy>
- All guidance, questions, and reports must be output in Korean (this command is exempt from the
settings.languagemechanism per the marketplace SPEC). - NEVER include a
Co-Authored-Bytrailer in any commit. AddingCo-Authored-Byheaders to AI-generated commits is strictly prohibited. - Execute git operations via
Bash. - For GitHub-related lookups, prioritize GitHub MCP; fall back to
ghCLI on failure. - Out of scope: changing a PR's base branch on GitHub; running tests after rebase; modifying PR metadata. </Execution_Policy>
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.
- 3d ago First seen · 192 lines · 151 tokens per session scan A 0dbb7fbe0a45
git-rebase-stack is a command published in the GitHub repository hg-pyun/claude-code-marketplace (2 stars, last pushed 2mo ago), licensed MIT. It adds 151 tokens to every session and 2,567 once invoked, about $0.0008 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-31.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.