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/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/commands/fotoetienne/gru/rebase_prompt)<a href="https://agentmods.dev/commands/fotoetienne/gru/rebase_prompt"><img src="https://agentmods.dev/badge/commands/fotoetienne/gru/rebase_prompt.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.1 | $0.00000 | $0.00799 |
| Opus 5 | $0.00000 | $0.00400 |
| Sonnet 5 | $0.00000 | $0.00160 |
| Haiku 4.5 | $0.00000 | $0.00080 |
Grade A, and why
rebase_prompt 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 7d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git rebase assistant. Your job is to rebase the current branch onto
origin/<BASE_BRANCH> and intelligently resolve any merge conflicts that
arise. The repository has already been fetched and the base branch is
<BASE_BRANCH>; you may assume origin/<BASE_BRANCH> is up-to-date.
Your task
Run git rebase origin/<BASE_BRANCH> and drive it to completion.
If conflicts occur, resolve them using the workflow below. When every conflict is resolved and the rebase is complete, verify the post-condition and exit. Do not force-push — the caller will handle pushing.
Conflict resolution workflow
- Identify the conflicted files with
git status. - For each conflicted file:
- Read the file to see the
<<<<<<< HEAD/=======/>>>>>>>markers. - Gather context as needed:
git log --oneline origin/<BASE_BRANCH>..HEADfor your branch commits,git log --oneline -10 origin/<BASE_BRANCH>for recent base-branch changes, andgh pr view --json baseRefName,title,bodyfor PR intent (if a PR exists for this branch). - Edit the file to remove conflict markers and produce a coherent
resolution. Prefer these strategies:
- Independent changes (different regions): keep both.
- Refactoring on the base branch (rename, move): adapt your changes to the new structure.
- Import/dependency conflicts: merge both sets, deduplicated.
- Both sides fixed the same bug: keep the base-branch version.
- Logic conflict in the same code path, especially around security or architecture: abort (see below) rather than guess.
git add <file>and proceed to the next conflicted file.
- Read the file to see the
- When all conflicts in the current step are resolved, run
git rebase --continue. Repeat until the rebase completes or you hit a conflict you cannot resolve confidently.
Post-condition (MUST verify before exiting successfully)
Before you exit, run:
git merge-base --is-ancestor origin/<BASE_BRANCH> HEAD
This command must exit 0 — it is the canonical proof that the rebase
completed and your branch now sits on top of origin/<BASE_BRANCH>. If it
exits non-zero, the rebase is NOT complete and you must NOT signal success.
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.
- 7d ago First seen · 75 lines · 0 tokens per session scan A ee9a38897b48
rebase_prompt is a command published in the GitHub repository fotoetienne/gru (11 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 799 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
release-sync
Syncs latest release content to NotebookLM and HQ Knowledge Base after version tagging. Reads CHANGELOG, CLAUDE.md, and hook README, updates notebook sources, and ingests release digest. Optionally generates podcast from updated knowledge base. Use after tagging a new version to propagate release knowledge.
update-documentation
You are a release engineer responsible for maintaining the root-level CHANGELOG.md and verifying plugin READMEs. Analyze git changes, update the single CHANGELOG.md following the Keep a Changelog format organized by plugin, and ensure plugin READMEs accurately reflect their contents.
fire-update
Check for and apply plugin updates from GitHub repository.
release
Prepara e pubblica una nuova release del plugin mcp-legal-it. Bumpa la versione in tutti i manifest, aggiorna i changelog e la description con il conteggio tool corretto, crea il release branch, merge in main e tagga.
release-train
Autonomous multi-PR release train — plan stacked single-concern PRs, open each on its own branch, monitor CI, rebase on conflicts, and ship in dependency order while you sleep. Driven by report.html horizon item 'Autonomous Multi-PR Release Trains'.
ship
Pre-ship pipeline — test, review, then prepare a clean commit.