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/sjungling/sjungling-claude-pluginsWrote 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/sjungling/sjungling-claude-plugins/rebase-main)<a href="https://agentmods.dev/commands/sjungling/sjungling-claude-plugins/rebase-main"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/rebase-main/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/sjungling/sjungling-claude-plugins/rebase-main"><img src="https://agentmods.dev/badge/commands/sjungling/sjungling-claude-plugins/rebase-main.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.00013 | $0.00568 |
| Opus 5 | $0.00006 | $0.00284 |
| Sonnet 5 | $0.00003 | $0.00114 |
| Haiku 4.5 | $0.00001 | $0.00057 |
Grade A, and why
rebase-main 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 10d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase the current branch against main. Follow this workflow exactly:
Step 1: Detect Environment
Run these commands to determine context:
!git rev-parse --show-toplevel
!git worktree list
!git branch --show-current
!git status --porcelain
From these results, determine:
- Current branch name (from
git branch --show-current) - Is this a worktree? — If
git worktree listshows more than one entry AND the current working directory is NOT the first (main) worktree listed, then we are in a linked worktree - Has uncommitted changes? — If
git status --porcelainproduces output - Main worktree path — The first entry in
git worktree list(the bare/main worktree)
Step 2: Stash if needed
If there are uncommitted changes (staged or unstaged):
- Run
git stash push -m "rebase-main: auto-stash before rebase" - Remember that we stashed so we can pop later
Step 3: Rebase based on context
Case A: In a worktree
Fetch the latest main from origin and rebase against it. Do NOT try to update the local main ref — git refuses to update a branch that is checked out in another worktree.
- Run
git fetch origin main - Run
git rebase origin/main
Case B: Not in a worktree, ON main branch
We're on main itself — rebase against origin:
- Run
git fetch origin main - Run
git rebase origin/main
Case C: Not in a worktree, on a NON-main branch
Rebase against the local main branch:
- Run
git rebase main
Step 4: Handle rebase conflicts
If the rebase fails due to conflicts:
- Report the conflicting files to the user
- Ask the user how they want to proceed: resolve conflicts, or abort with
git rebase --abort - Do NOT automatically resolve conflicts — wait for user guidance
Step 5: Restore stash
If we stashed changes in Step 2:
- Run
git stash pop - If the stash pop has conflicts, report them to the user
Step 6: Report results
Summarize what happened:
- Which rebase case was used (worktree/main/branch)
- Whether changes were stashed and restored
- Current branch status after rebase
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.
- 10d ago First seen · 65 lines · 13 tokens per session scan A 50c44147c9a9
rebase-main is a command published in the GitHub repository sjungling/sjungling-claude-plugins (13 stars, last pushed 27d ago), licensed MIT. It adds 13 tokens to every session and 568 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-08-30.
Other commands, from other repositories
commit
A command that examines staged Git changes and proposes a commit message using the Conventional Commits format, such as feat, fix, or docs. Git is a tool for tracking changes to code.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
handoff
Export a Waybill Bundle by default, or import one when requested.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.