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.
npx agentmods add agents/auerbachb/claude-code-config/phase-c-mergergit clone --depth 1 https://github.com/auerbachb/claude-code-configWhat 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.00027 | $0.03951 |
| Opus 5 | $0.00014 | $0.01975 |
| Sonnet 5 | $0.00005 | $0.00790 |
| Haiku 4.5 | $0.00003 | $0.00395 |
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 2d 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 — 255 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 path
if ! path=$(resolve_script "$name"); then
echo "ERROR: $name not found (checked ~/.claude/skills-worktree/.claude/scripts/, ~/.claude/scripts/, .claude/scripts/)" >&2
return 127
fi
"$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).
Read reference docs the same way, $HOME/.claude/skills-worktree/.claude/reference/<name> first. Rules under .claude/rules/*.md need no fallback — they auto-load at user scope in every project.
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.
- 2d 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 3d ago), licensed MIT. It adds 27 tokens to every session and 3,951 once invoked, about $0.0001 per session on Opus 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
quality-engineer
Quality-lens reviewer covering testability, observability, reliability, and maintainability -- the "cost to live with this code" pass. Also drafts contract or construction tests on request. Reads effective repository guidance, the spec and plan if any, the diff, and nearby tests; flags test-shape problems (wrong…
adversarial-reviewer
Adversarial reviewer for specs, plans, implementations, or any combination ("spec amendment + implementation in the same PR" is the dominant case). Loads project conventions and the targeted artifacts; attacks along the relevant checklists; returns severity-labeled findings. Use after gates pass but before declaring…
review-all-shared-rules
Shared severity tiers, verification gate, quotas, and auto-drop rules included by every review-all agent prompt.
skill-editor
Applies a single, minimal, generalized edit to a Logic-Lens skill (SKILL.md / guide / shared file) given a concrete failure diagnosis. Use inside the iteration loop after eval-failure-analyzer has produced a proposal, to turn that proposal into an actual edit. Mutates files; does NOT run evals or sync the cache — it…
bugs-and-security
Scan changed code for logic bugs, security vulnerabilities (OWASP Top 10), completeness gaps, and error handling issues.
security-deep-dive
Conditional threat-model analysis with adversarial reasoning, attack scenarios, and CWE classification. Distinct from agent 02 (which does broad pattern scanning).