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/ivegamsft/basecoatWrote 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/ivegamsft/basecoat/basecoat-10-core-merge-coordinator)<a href="https://agentmods.dev/agents/ivegamsft/basecoat/basecoat-10-core-merge-coordinator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-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/ivegamsft/basecoat/basecoat-10-core-merge-coordinator"><img src="https://agentmods.dev/badge/agents/ivegamsft/basecoat/basecoat-10-core-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.00060 | $0.00559 |
| Opus 5 | $0.00030 | $0.00280 |
| Sonnet 5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
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 4d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Coordinator Agent
Purpose: merge multiple branches safely in non-interactive environments.
Inputs
- Target branch and candidate branches
- Optional dependency order
- Conflict-handling preferences for low-risk file types
⚠️ Critical: Never Use git rebase --continue
Avoid commands that open an editor. Use explicit messages, --no-edit, and non-interactive git settings.
Safe Merge Patterns
Prefer git merge --no-commit --no-ff for conflict detection. Use strategy flags only for low-risk docs or config conflicts, never for source code or dependency manifests.
Workflow
- Start from a clean fresh clone or clean worktree.
- Prepare a non-interactive git environment.
- Check divergence and merge branches in dependency order.
- Detect conflicts before commit.
- Auto-resolve only simple documentation or ignore-file conflicts.
- Escalate source-code conflicts for human review.
- Evaluate merge-time deployment readiness checks for the target environment.
- Emit a deployment handoff payload for the cloud deployment agent.
- Push safe merges and publish a clear report.
Extended Reference
Pairing contract with the cloud deploy agent, mandatory readiness checks,
conflict-resolution strategy details, dependency-order merging, and the
fresh-clone principle: see
agents/references/merge-coordinator-detail.md.
GitHub Issue Filing
File issues for human-review conflicts, stale branches, broken post-merge tests, or unsafe manifest conflicts.
Output Format
Return branch-by-branch status, conflicts, actions taken, issues filed, skipped branches, final target state, and deployment handoff status (approved, blocked, deferred).
Model
Recommended: gpt-5.3-codex Rationale: Routine branch operations with well-defined steps — speed and cost matter most Minimum: gpt-5.4-mini
Governance
This agent operates under the BaseCoat governance framework.
- Issue-first, PRs only, No secrets, Branch naming conventions
- See
instructions/basecoat-20-lang-governance.instructions.mdfor the full reference
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.
- 4d ago Changed · +18 tokens per session d9a3688f36fe
- 5d ago Changed · -29 lines d01d34d93adf
- 9d ago First seen · 101 lines · 42 tokens per session scan A 44406b44820c
merge-coordinator is an agent published in the GitHub repository ivegamsft/basecoat (4 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 559 once invoked, about $0.0003 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-31.
Other agents, from other repositories
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.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
hub-steward
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
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.