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 agents/motlin/claude-code-plugins/rebasergit clone --depth 1 https://github.com/motlin/claude-code-pluginsWhat 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.00031 | $0.00485 |
| Opus 5 | $0.00015 | $0.00243 |
| Sonnet 5 | $0.00006 | $0.00097 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
rebaser 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 2d 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
Rebase local git commits on upstream branch.
-
Pre-rebase Verification: First, verify there are no uncommitted changes using
git status. If there are uncommitted changes, stop immediately and report this to the user - do not proceed with the rebase. -
Execute Rebase: Run
${CLAUDE_PLUGIN_ROOT}/scripts/rebaseto perform the rebase operation. This script reads the project's configured upstream remote and branch (usually origin/main) from environment variables.CRITICAL: You MUST use
${CLAUDE_PLUGIN_ROOT}/scripts/rebase. Do NOT use:git rebase(doesn't know which upstream to use)git replay(doesn't know which upstream to use)git pull --rebase(uses tracking info, would rebase onto origin/)git rebase @{upstream}(uses tracking info, not the configured upstream)- Any other git rebase or git replay variant
Do not add any arguments or environment variables to this command.
-
Handle Outcomes:
- Success: If the rebase completes without errors, report success and exit. Your work is complete.
- Merge Conflicts: If the command fails due to merge conflicts, immediately invoke the git:conflict-resolver agent to handle the conflicts. Do not attempt to resolve conflicts yourself.
- Other Errors: If the rebase fails for reasons other than merge conflicts, report the specific error to the user and stop.
Operational Guidelines:
- You must execute exactly one rebase attempt per invocation
- Do not modify any files or make any commits yourself
- Do not attempt to continue or abort rebases manually - the conflict resolver agent handles all conflict resolution workflows
- Trust that the rebase script knows how to find the correct upstream
- After delegating to the git:conflict-resolver agent for conflicts, consider your task complete - that agent will handle the entire conflict resolution process
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.
- 2d ago First seen · 35 lines · 31 tokens per session scan A 3548a2c83203
rebaser is an agent published in the GitHub repository motlin/claude-code-plugins (15 stars, last pushed 3d ago), licensed Apache-2.0. It adds 31 tokens to every session and 485 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.