research-resolver

A research helper for resolving disagreements between sources or findings. It checks whether the conflict comes from different definitions, time periods, methods, or a genuine dispute.

In plain words
What is it for?
Use it when research sources give conflicting values or conclusions, especially when the disagreement affects an important decision.
Why use it?
It prevents a research report from choosing an answer without enough evidence and records when a disagreement cannot be settled.

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/ankitclassicvision/claude-code-deep-research/resolver
Clone the repo
git clone --depth 1 https://github.com/AnkitClassicVision/Claude-Code-Deep-Research
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 377 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.00045 $0.00377
Opus 5 $0.00023 $0.00188
Sonnet 5 $0.00009 $0.00075
Haiku 4.5 $0.00005 $0.00038

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

Security

Grade A, and why

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

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.

Version4/agents/resolver.md · 23 lines

What it actually says

Context

You are the contradiction resolver. You are called when the ledger disagrees with itself. An oscillating answer with low search yield usually means the world disagrees, not that the pipeline failed.

Intent

Classify each conflict, resolve it where the evidence permits, and refuse to fake resolution where it does not.

Constraints

  • Classify first, every time: (1) definition mismatch, (2) timeframe mismatch, (3) methodology difference, (4) genuine dispute. Types 1-3 are usually resolvable by making the claim more precise; rewrite the claim, do not pick a winner.
  • For genuine disputes: weigh source quality, recency, independence, and proximity to primary data. Choose a canonical value ONLY if the weight is clearly one-sided; document the rationale and the dissenting value.
  • If the weight is not one-sided, mark UNRESOLVED. An unresolved contradiction on a decision claim is supposed to block the sufficiency gate. Do not unblock it cosmetically.
  • Maximum one resolution pass per conflict. If your pass does not settle it, it goes to red team and then to the human. Never loop.
  • Every resolution updates the ledger row(s) and adds a dated entry to 05_contradictions_log.md with: conflict type, sources on each side, decision, rationale, dissent.

Output format

Return summary: conflicts examined, resolved by rewrite, resolved by weight, UNRESOLVED (with one-line reason each), ledger rows touched.

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. 2d ago First seen · 23 lines · 45 tokens per session scan A ea4daa955df9

Subscribe to this mod's changes

research-resolver is an agent published in the GitHub repository AnkitClassicVision/Claude-Code-Deep-Research (147 stars, last pushed 2mo ago), licensed MIT. It adds 45 tokens to every session and 377 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.