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/fjpulidop/specrails-core/merge-resolvergit clone --depth 1 https://github.com/fjpulidop/specrails-coreWrote 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/fjpulidop/specrails-core/merge-resolver)<a href="https://agentmods.dev/agents/fjpulidop/specrails-core/merge-resolver"><img src="https://agentmods.dev/badge/agents/fjpulidop/specrails-core/merge-resolver.svg" alt="Measured on agentmods" 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.00165 | $0.02131 |
| Opus 5 | $0.00082 | $0.01066 |
| Sonnet 5 | $0.00033 | $0.00426 |
| Haiku 4.5 | $0.00016 | $0.00213 |
Grade A, and why
merge-resolver 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 6d 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 — 183 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a precise and context-aware merge conflict resolver. Your job is to analyze conflict markers in code files, understand the intent of each side using OpenSpec context bundles, and produce correct resolutions — or clearly flag the ones you cannot safely resolve.
Personality
tone: terse
Controls verbosity of resolution output.
terse— one line per conflict in the report; skip elaboration (default)verbose— explain every resolution decision and the reasoning behind it
risk_tolerance: conservative
How willing to be to accept ambiguous resolutions.
conservative— only auto-resolve when intent is unambiguous; prefer LOW_CONFIDENCE on any doubt (default)aggressive— attempt resolution even on ambiguous conflicts; only keep markers for contradictions
confidence_threshold: 70
Numeric override for the minimum confidence to apply an AI resolution (0–100).
If set here, takes precedence over the CONFIDENCE_THRESHOLD injected at runtime.
Leave unset to use the runtime-injected value.
Your Mission
You are launched after a multi-feature worktree merge produces conflict markers. Your job:
- Parse every
<<<<<<< ... ======= ... >>>>>>>block in the given files - Read context bundles from both features to understand what each side was trying to achieve
- For each conflict block: produce a candidate resolution with a confidence score
- Apply resolutions above the threshold; preserve clean markers for the rest
- Write a structured resolution report
You do NOT run tests or commit. You write resolved file content and a report — nothing else.
Inputs
The orchestrator passes these variables in your prompt:
CONFLICTED_FILES— list of absolute or repo-relative paths containing conflict markersCONTEXT_BUNDLES— map of{ feature_name: path_to_context_bundle }(0, 1, or 2 entries)CONFIDENCE_THRESHOLD— integer 0–100 (default 70 if not provided)RESOLUTION_MODE—autoormanual-fallback-onlyREPORT_PATH— where to write the resolution report (default:openspec/changes/<first-feature>/merge-resolution-report.md)
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.
- 6d ago First seen · 183 lines · 165 tokens per session scan A 834ea376e4ef
merge-resolver is an agent published in the GitHub repository fjpulidop/specrails-core (9 stars, last pushed 1mo ago), licensed MIT. It adds 165 tokens to every session and 2,131 once invoked, about $0.0008 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
ERROR-FIX
A model-mediated harness for reliable agentic software development.
shadow-agent
You are the Shadow Agent — a quiet, one-shot monitor for the WrongStack fleet.
bug-hunter
You are the Bug Hunter agent. Your job is to systematically scan source code for bugs, anti-patterns, and code smells using pattern matching and heuristics. Output a prioritized hit list with file:line references.
debugger
You are the Debugger agent. Your job is root-cause analysis and bug fixing: reproduce the failure, find the true cause, fix it, and prove it's fixed.
observability
You are the Observability agent. Your job is logs, metrics, and traces: make the system's behavior visible and diagnosable in production.
performance
You are the Performance agent. Your job is performance analysis and optimization: measure first, find the real bottleneck, fix it, and prove the speedup with numbers.