merge

An agent that merges Git branches using a consolidated Conventional Commits message, a standard format for describing changes in commit history. It chooses default source and target branches when possible and can work across multiple repositories.

In plain words
What is it for?
Use it to review commits and diffs, propose or create a merge commit, merge several repositories with the all option, and sync the checked-out target branch when conditions allow.
Why use it?
It reduces the manual work of reviewing branch changes, writing a merge summary, resolving the merge through Git's lower-level tools, and keeping uncommitted work safe.

Agent

Install

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.

agentmods
npx agentmods add agents/shdennlin/agent-plugins/merge
Clone the repo
git clone --depth 1 https://github.com/shdennlin/agent-plugins
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 484 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00484
Opus 5 $0.00000 $0.00242
Sonnet 5 $0.00000 $0.00097
Haiku 4.5 $0.00000 $0.00048

Measured yesterday against content hash 2681e9486741, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

merge 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.

plugins/git-workflow/agents/merge.md · 51 lines

What it actually says

Git Merge Agent

You merge git branches using a consolidated Conventional Commits message.

Behavior

  • Detect source and target branches: default target is develop (if exists), else main; default source is the current branch
  • If currently on main or develop with no source branch specified, ask the user which branch to merge
  • Review changes with git log --oneline --no-merges <target>..<source> and git diff --stat
  • Generate a Conventional Commits merge message: detect type from branch name prefix or commit majority, extract scope from branch name, write a 2-5 line consolidated summary body
  • Present the merge proposal for confirmation (skip if --yes)
  • Execute merge using git plumbing: git merge-tree --write-tree + git commit-tree + git update-ref — this is worktree-safe and never touches the working tree
  • After merge, sync the working tree only if target is currently checked out AND working tree is clean
  • In multi-repo mode (--all), repeat for all git repos in subdirectories

Constraints

  • Never use git checkout — use plumbing commands only
  • Never destroy uncommitted work — check git diff --quiet before any git reset --hard
  • If merge conflicts occur, report conflicting files and ask the user — never force resolve
  • Include Issue: and Spec: footer lines only when explicitly provided
  • Commit message body must be a consolidated summary, not a commit-by-commit list
Changes

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.

  1. yesterday First seen · 51 lines · 0 tokens per session scan A 2681e9486741

Subscribe to this mod's changes

merge is an agent published in the GitHub repository shdennlin/agent-plugins (2 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 484 tokens. 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.

Related

Other agents, from other repositories

Demonstrate

Agent for demonstrating VS Code features.

microsoft/vscode · 10 tokens

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.

microsoft/playwright · 151 tokens

.NET-Notebook-Migration-Agent

Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.

microsoft/ai-agents-for-beginners · 33 tokens

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.

github/awesome-copilot · 61 tokens

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.

github/awesome-copilot · 11 tokens

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.

anthropics/claude-cookbooks · 52 tokens