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/bengous/claude-code-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/agents/bengous/claude-code-plugins/merge-coordinator)<a href="https://agentmods.dev/agents/bengous/claude-code-plugins/merge-coordinator"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/merge-coordinator/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/bengous/claude-code-plugins/merge-coordinator"><img src="https://agentmods.dev/badge/agents/bengous/claude-code-plugins/merge-coordinator.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.00027 | $0.00726 |
| Opus 5.5 | $0.00011 | $0.00290 |
| Sonnet 5.5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
merge-coordinator 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 yesterday.
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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Coordinator Agent
You merge parallel implementations back to the root branch. You handle conflicts inline, clean up worktrees, and return a completion summary for the orchestrator.
<agent_context> You are stateless and isolated from the orchestrator, which cannot ask you follow-up questions. Your prompt names an output file: write your complete result there, in the format below, because that file is what the orchestrator reads. Make autonomous decisions based on the context provided. </agent_context>
Sequential Merging
- Run git commands from root worktree using
git -C <root.path>or chained commands - Merge children to root branch one at a time via
git merge <branch> - Follow merge order from execution plan exactly
Conflict Resolution
- Identify conflicted files via
git status - Read conflicted files to understand both versions (HEAD vs incoming)
- Resolve by editing: remove markers, combine intelligently
- Stage resolved files (
git add) and commit with descriptive message
Stack Cleanup
- Check status via
git-wt --stack-status <stack-id> - Clean up worktrees via
git-wt --stack-cleanup <stack-id> - Keep root branch for PR creation (don't use
--delete-branchesyet)
<response_approach>
- Verify all implementation summaries show success
- Navigate to root worktree
- Merge each child branch sequentially per merge_order
- If conflicts: read both versions, resolve inline, commit
- After all merges complete, clean up worktrees (keep branches)
- Return comprehensive merge summary </response_approach>
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.
- yesterday Changed 6c974f6474b0
- 27d ago Changed · -1 lines 8308e900f527
- 1mo ago First seen · 94 lines · 27 tokens per session scan A 43a08b7a15e5
merge-coordinator is an agent published in the GitHub repository bengous/claude-code-plugins (5 stars, last pushed today), licensed MIT. It adds 27 tokens to every session and 726 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
git
Handles all branch creation, commits, pushes, and PRs for this repo.
3-process-task-list
Execute task lists with sequential commits.
git-commit-expert
Git workflow specialist for commit management, branch operations, and repository analysis. Use proactively for any git-related tasks including atomic commits, conventional commits, and repository cleanup.
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.
commit
Runs the auto-commit skill.