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 skills/fotoetienne/gru/git-rebasenpx skills add fotoetienne/gru --skill git-rebasegit clone --depth 1 https://github.com/fotoetienne/gruWrote 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/fotoetienne/gru/git-rebase)<a href="https://agentmods.dev/skills/fotoetienne/gru/git-rebase"><img src="https://agentmods.dev/badge/skills/fotoetienne/gru/git-rebase.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.00040 | $0.03107 |
| Opus 5 | $0.00020 | $0.01554 |
| Sonnet 5 | $0.00008 | $0.00621 |
| Haiku 4.5 | $0.00004 | $0.00311 |
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 4d 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 — 517 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git rebase assistant that helps rebase the current working branch onto the default branch with intelligent conflict resolution.
Your Role
Your primary task is to:
- Fetch the latest default branch from origin
- Rebase the current branch onto the default branch
- Intelligently resolve merge conflicts
- Look at PR and issue context when needed to understand intent
- Report any conflicts you cannot resolve confidently
Workflow
Step 1: Gather Context
Before starting the rebase:
# Get current branch
git branch --show-current
# Get default branch (usually main or master)
git remote show origin | grep "HEAD branch"
# Check current git status
git status
Important: Verify:
- Current branch is NOT the default branch
- Working directory is clean (no uncommitted changes)
- You're in a git repository
If there are uncommitted changes, stop and inform the user to commit or stash them first.
Step 2: Fetch Latest Default Branch
# Fetch the latest from origin
git fetch origin
# Verify the default branch exists
git branch -r | grep origin/<default-branch>
Step 3: Start the Rebase
# Start rebase onto the default branch
git rebase origin/<default-branch>
Step 4: Handle Conflicts
If conflicts occur, git will pause the rebase. You'll see:
CONFLICT (content): Merge conflict in <file>
For each conflict:
-
Identify conflicted files:
git status -
Read the conflicted file to understand the conflict markers:
<<<<<<< HEAD [default branch version] ======= [your branch version] >>>>>>> [commit] -
Gather context to make informed decisions:
a) Look at the commit messages:
# See what commits are being rebased git log --oneline origin/<default-branch>..HEAD # See recent commits on default branch git log --oneline -10 origin/<default-branch>b) Check PR context (if available):
# Get current PR (if in a PR branch) gh pr view --json number,title,body,url
What ships with it
1 file 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.
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.
- 4d ago First seen · 517 lines · 40 tokens per session scan A aa2767605956
git-rebase is a skill published in the GitHub repository fotoetienne/gru (11 stars, last pushed 27d ago), licensed Apache-2.0. It adds 40 tokens to every session and 3,107 once invoked, about $0.0002 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-30.
Other skills, from other repositories
mcporter
List, auth, and call MCP servers/tools from the terminal.
article-writing
Write articles, guides, blog posts, tutorials, newsletter issues, and other long-form content in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, especially when voice consistency, structure, and credibility matter.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
complete-partial-pr
Evaluate and complete an issue or PR where the submitted patch fixes only a narrow symptom of the reported pain point. Use when a contribution may miss adjacent integration surfaces, provider/spec semantics, roundtrip behavior, tests, docs, or historical maintainer decisions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…