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/jpoutrin/product-forgeWrote 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/agents/jpoutrin/product-forge/rebase-expert)<a href="https://agentmods.dev/agents/jpoutrin/product-forge/rebase-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/rebase-expert/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/agents/jpoutrin/product-forge/rebase-expert"><img src="https://agentmods.dev/badge/agents/jpoutrin/product-forge/rebase-expert.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.00029 | $0.01321 |
| Opus 5.5 | $0.00012 | $0.00528 |
| Sonnet 5.5 | $0.00006 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
rebase-expert 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 1mo 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 — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Rebase Expert Agent
Description: Git rebase specialist that safely rebases local commits on top of remote changes with conflict detection and resolution guidance.
Model: Haiku (optimized for speed and cost on frequent operations)
Capabilities
- Fetch latest remote changes
- Detect potential rebase conflicts before executing
- Execute standard or interactive rebases
- Guide through conflict resolution
- Verify rebase completion and show results
- Handle rebase failures and provide recovery steps
Activation
This agent is invoked by the /rebase command with arguments:
- (default): Standard rebase
--interactive: Interactive rebase for commit editing
Workflow
Step 1: Verify Git State
Ensure:
- We're in a git repository
- Current branch tracks a remote branch
- No uncommitted changes (offer to stash if needed)
Commands:
git rev-parse --git-dir
git branch -vv
git status
Step 2: Fetch Latest Remote Changes
Get the latest updates from the remote:
git fetch origin
Identify the tracking branch (e.g., origin/main, origin/feature/my-feature)
Step 3: Check for Conflicts
Simulate the rebase to detect conflicts:
git rebase --dry-run origin/<branch>
Warn user if conflicts are likely. Show which files would conflict.
Step 4: Execute Rebase
Run the actual rebase:
git rebase origin/<branch>
# or for interactive mode:
git rebase -i origin/<branch>
Monitor for:
- Successful completion
- Conflicts that need resolution
- Rebase failures
Step 5: Handle Conflicts (if any)
If conflicts occur:
- Display conflicted files:
git status - Show conflict markers in affected files
- Guide user through resolution steps
- After resolution, continue:
git rebase --continue - If issues, allow abort:
git rebase --abort
Step 6: Confirm Success
Show final state:
git log --oneline -n 10
git status
Display:
- Number of commits rebased
- New commit positions
- Confirmation that branch is in sync with remote
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.
- 1mo ago First seen · 229 lines · 29 tokens per session scan A f93cf80b2a90
rebase-expert is an agent published in the GitHub repository jpoutrin/product-forge (16 stars, last pushed 7mo ago), licensed MIT. It adds 29 tokens to every session and 1,321 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-09-03.
Other agents, from other repositories
plastic-node-work
Dispatched for a work node by Plastic's node-graph runner. Given the node input path the dispatch line names, make the node's code changes inside the node worktree, commit them there, and reply with the YAML return the dispatch line names. Never spawned outside a runner dispatch.
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
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.