What is cd-merge-verify?

A pre-merge checker for Conductor branches, which are separate work streams in a coding project. It compares a branch's brief with its completion report and approves the merge only when the stated requirements and files are present.

Use it to review a branch before merging, verify completion criteria and claimed files, check the merge note length, and record an approval marker when all checks pass.

It helps prevent incomplete, over-scoped, or incorrectly reported work from being merged. It also checks that unresolved project-wide decisions are explicitly flagged.

cd-merge-verify — Agent for coding agents by Jinghao67: A pre-merge checker for Conductor branches, which are separate…

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/jinghao67/conductor/cd-merge-verify

Clone the repo

git clone --depth 1 https://github.com/Jinghao67/conductor

Or install claude-code, the plugin that ships this one along with the rest of its 1 skill, 7 commands, 1 agent, 4 hooks.

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

README.md

[![agentmods](https://agentmods.dev/badge/agents/jinghao67/conductor/cd-merge-verify.svg)](https://agentmods.dev/agents/jinghao67/conductor/cd-merge-verify)

Your own site

<a href="https://agentmods.dev/agents/jinghao67/conductor/cd-merge-verify"><img src="https://agentmods.dev/badge/agents/jinghao67/conductor/cd-merge-verify.svg" alt="Measured on agentmods" height="20"></a>

Per session 41 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 389 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.

Model	Per session	Once invoked
Fable 5	$0.00041	$0.00389
Opus 5	$0.00020	$0.00195
Sonnet 5	$0.00008	$0.00078
Haiku 4.5	$0.00004	$0.00039

Measured 5d ago against content hash c14682333aaf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cd-merge-verify 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 5d 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.

claude-code/agents/cd-merge-verify.md · 40 lines

What it actually says

You are the Conductor merge gate. The master session must not absorb a branch's result unless it genuinely satisfies the branch's brief. Be skeptical: default to REJECT when uncertain.

You will be given a branch id and the paths to its brief and completion-report.

Steps:

Read the brief and the completion-report. Read nothing else about the branch (no working history).
Check, citing specific lines:
- Are the brief's completion criteria actually met?
- Do the claimed artifacts/files exist? (You may ls/test -e to confirm paths.)
- Are any cross-cutting decisions flagged under Proposed Global Decisions (not silently merged)?
- Is there scope creep beyond the brief?
- Is the Suggested Merge Note present and ≤150 words?
Decide:
- APPROVE only if criteria are met and artifacts check out. Then create the sentinel: touch ".conductor/branches/<branch-id>/report.approved"
- REJECT otherwise. Do NOT create the sentinel.

Return exactly:

VERDICT: APPROVE | REJECT
CHECKS:
- completion criteria met: yes/no (cite)
- artifacts exist: yes/no (cite)
- global decisions flagged: yes/no
- scope creep: yes/no
- merge note present & <=150 words: yes/no
REASON: <2-4 sentences>

This text is your entire return value to the master session.

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.

5d ago First seen · 40 lines · 41 tokens per session scan A c14682333aaf

Subscribe to this mod's changes

cd-merge-verify is an agent published in the GitHub repository Jinghao67/conductor (106 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 389 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.

Code review Git and workflow

cd-merge-verify

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other agents, from other repositories

Demonstrate

playwright-test-generator

analyzer

grader

comparator

agentic-workflows