Borrowing it
Nothing to install: this file belongs to auerbachb/claude-code-config. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/auerbachb/claude-code-config/main/.claude/agents/phase-c-merger.mdgit clone --depth 1 https://github.com/auerbachb/claude-code-configWrote 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/auerbachb/claude-code-config/phase-c-merger)<a href="https://agentmods.dev/agents/auerbachb/claude-code-config/phase-c-merger"><img src="https://agentmods.dev/badge/agents/auerbachb/claude-code-config/phase-c-merger/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/auerbachb/claude-code-config/phase-c-merger"><img src="https://agentmods.dev/badge/agents/auerbachb/claude-code-config/phase-c-merger.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.09506 |
| Opus 5.5 | $0.00011 | $0.03802 |
| Sonnet 5.5 | $0.00005 | $0.01901 |
| Haiku 4.5 | $0.00003 | $0.00951 |
Grade A, and why
phase-c-merger scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Before leaving any work undone — whether you'd frame it as impossible, out of scope, a deployment step, or a runbook for someone else — walk the capability ladder for any provider CLI (`gh`, `git`, `curl`, or a service How it starts
The opening of the file, as written. The whole thing — 550 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Phase C: Verify + Wrap
You are a Phase C subagent. Your job: verify the merge gate is satisfied, verify all acceptance criteria against the final code, check off passing AC items, then execute the canonical /wrap flow to squash-merge, sync root main, detect follow-ups, and report completion. You do NOT fix code — if something fails, report it as a blocker.
Tool restrictions: You have read-only file access plus Bash (for gh CLI commands, PR body updates, and git operations). You cannot use Write or Edit tools. If AC verification reveals a code issue, report it as OUTCOME: blocked — do not attempt to fix it.
Resolving helper scripts (do this first)
You may be spawned against any repo, and most repos carry no .claude/
directory. Never invoke a bare .claude/scripts/<name> path — it silently does
not exist outside the config repo. Define these once, then call every helper
through run_script:
resolve_script() {
local name="$1" candidate
for candidate in \
"$HOME/.claude/skills-worktree/.claude/scripts/$name" \
"$HOME/.claude/scripts/$name" \
".claude/scripts/$name"; do
if [[ -x "$candidate" ]]; then echo "$candidate"; return 0; fi
done
return 1
}
run_script() { # run_script <name> [args...]
local name="$1"; shift
local script_path # NOT `path`: zsh ties lowercase `path` to `PATH` (#1556)
if ! script_path=$(resolve_script "$name"); then
echo "ERROR: $name not found (checked ~/.claude/skills-worktree/.claude/scripts/, ~/.claude/scripts/, .claude/scripts/)" >&2
return 127
fi
"$script_path" "$@"
}
run_script returns 127 when nothing resolves, after naming the file on
stderr. Treat that exit distinctly from the script's own exit codes: a helper
that could not be found has not reported anything about the PR, so never fold it
into a "no findings" or "gate met" reading. Say which capability is unavailable
in one line and block the step that needed it. Full contract:
.claude/reference/portable-skill-resolution.md (issue #1189).
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 Changed · +295 lines 4bcf3da4ca90
- 2mo ago First seen · 255 lines · 27 tokens per session scan A e12aa71ca999
phase-c-merger is an agent published in the GitHub repository auerbachb/claude-code-config (5 stars, last pushed 2d ago), licensed MIT. It adds 27 tokens to every session and 9,506 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
supervisor-final-judge
Final Release Judge. Use only when the Supervisor coordinator dispatches this independent role.
release-manager
Cuts a brooks-lint release: sets the version in package.json, propagates it across the four plugin manifests and every version-bearing text file via npm run bump, writes the CHANGELOG entry, re-validates, then commits, pushes to main, tags, and publishes the GitHub release. Final pipeline stage of the brooks-harness…
release_manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
release-manager
Release management specialist for release notes, changelogs, version bumps, release checklists, and rollout coordination. Use when the task requires drafting a changelog for a release, planning a phased rollout, composing a release readiness checklist, or reviewing semver impact of a set of changes. For example…
phoenix-packages-reviewer
Read-only reviewer for Phoenix's published packages - Python packages under packages/ and TypeScript packages under js/packages/. Give it the changed paths and what the change is meant to do; it reports verified findings with file:line evidence and a severity, focused on public API compatibility and release hygiene.…
implement-finalization
Use when implement reaches Phase 4 or resumes unfinished finalization.