Borrowing it
Nothing to install: this file belongs to compozy/kb. 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/compozy/kb/main/.agents/skills/git-rebase/SKILL.mdgit clone --depth 1 https://github.com/compozy/kbWrote 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/skills/compozy/kb/git-rebase)<a href="https://agentmods.dev/skills/compozy/kb/git-rebase"><img src="https://agentmods.dev/badge/skills/compozy/kb/git-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/skills/compozy/kb/git-rebase"><img src="https://agentmods.dev/badge/skills/compozy/kb/git-rebase.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00032 | $0.00584 |
| Opus 5.5 | $0.00013 | $0.00234 |
| Sonnet 5.5 | $0.00006 | $0.00117 |
| Haiku 4.5 | $0.00003 | $0.00058 |
Grade A, and why
git-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 25d 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
Git Rebase
Carry out the requested rebase while preserving both sides' intended behavior and unrelated work. A rebase request does not by itself authorize squashing, dropping commits, changing global Git settings, or publishing a rewritten branch.
- Inspect status, current branch, target, and any in-progress rebase. Reuse a known target and current fetch evidence. Preserve dirty work; do not auto-stash, reset, checkout, clean, or stage unrelated paths. Use an isolated checkout when needed.
- Before starting a new rebase, record HEAD and keep a backup ref when rewriting valuable history.
bash <skill-dir>/scripts/pre-rebase-backup.shcreates a backup for a clean branch without modifying tracked files. An existing verified backup needs no duplicate. - Rebase onto the requested target directly by default. Use interactive/squash/reorder operations only when the user requested that history change; commit count is not a reason to squash. Consult
references/strategies.mdfor an actual strategy decision. - When conflicts occur, inspect the replayed commit, base, and both sides. During rebase,
oursis the target plus commits already replayed;theirsis the commit being replayed. Trace changed APIs and preserve intended security, state, and compatibility contracts rather than accepting one side wholesale. - Resolve the affected files, inspect their diff, stage only those resolved paths, then continue. Reuse valid observations for repeated conflicts. Do not add merge-history comments to production code or run a full suite after every file.
- At the completed rebase, inspect the resulting patch series/diff and run checks for affected behavior plus the project's required delivery gate. Tests that expose a regression require a production fix, not weaker assertions.
- Publish only when already authorized. Use
--force-with-leasefor a rewritten remote branch, and follow the project's current-head CI policy. If the lease fails, inspect the new remote commits; do not replace it with unconditional force.
Use references/resolution-patterns.md for semantic conflicts and references/troubleshooting.md for diagnosed operational failures. Helpers live under this skill's actual scripts/ path; analyze-conflicts.sh/validate-merge.sh are optional aids after checking their repository assumptions. They do not replace the owning tests or gate. Recovery that discards work still needs the repository's explicit permission; a backup ref is evidence, not permission to reset.
What ships with it
8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/automation.md 740 B
- references/resolution-patterns.md 2.0 KB
- references/scripts-tools.md 711 B
- references/strategies.md 1.1 KB
- references/troubleshooting.md 1.1 KB
- scripts/analyze-conflicts.sh 2.9 KB runs code
- scripts/pre-rebase-backup.sh 1.1 KB runs code
- scripts/validate-merge.sh 3.0 KB runs code
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.
- 25d ago Changed · -36 lines · -1 tokens per session bd5793cc45c0
- 1mo ago First seen · 59 lines · 33 tokens per session scan A 6eeb7540ca0e
git-rebase is a skill published in the GitHub repository compozy/kb (112 stars, last pushed 3d ago), licensed MIT. It adds 32 tokens to every session and 584 once invoked, about $0.0001 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-30.
Other skills, from other repositories
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.