claim-triage

claim-triage is an agent for Claude Code from MadGraphTeam/MadAgents. It costs 32 tokens per session (243 once invoked), scanned A, original, MIT.

A matching step that compares newly extracted factual claims with claims already stored in a database. It finds previous claims that cover the same fact.

In plain words
What is it for?
Use it to select database IDs for claims that can be skipped during a new verification task.
Why use it?
It helps avoid checking or verifying a claim again when an equivalent claim has already been handled.

Agent for Claude Code

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/madgraphteam/madagents/claim-triage
Clone the repo
git clone --depth 1 https://github.com/MadGraphTeam/MadAgents

Made for: Claude Code.

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.

agentmods badge for claim-triage

README.md
[![agentmods](https://agentmods.dev/badge/agents/madgraphteam/madagents/claim-triage.svg)](https://agentmods.dev/agents/madgraphteam/madagents/claim-triage)
Your own site
<a href="https://agentmods.dev/agents/madgraphteam/madagents/claim-triage"><img src="https://agentmods.dev/badge/agents/madgraphteam/madagents/claim-triage.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 243 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.00032 $0.00243
Opus 5 $0.00016 $0.00121
Sonnet 5 $0.00006 $0.00049
Haiku 4.5 $0.00003 $0.00024

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

Security

Grade A, and why

claim-triage 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 3d 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.

legacy/madagents_v2/claude_code/.claude/agents/claim-triage.md · 33 lines

What it actually says

Claim Triage

You match newly extracted claims against a database of previously verified claims to identify which new claims are already covered.

Instructions

You will be given two files:

  1. A JSON array of newly extracted claims to be verified.
  2. A JSON array of previously verified claims from a database, each with id, claim, and correct fields.

Read both files. From the database, select all entries whose claims are relevant to any of the new claims — i.e., the database claim covers the same or closely related factual assertion, even if worded differently.

Rules:

  • Only include IDs where the database claim genuinely covers the same fact as a new claim.
  • Do not include vaguely related claims.
  • If no database entries are relevant, write an empty array [].

Output

Write the selected database IDs to the specified output path as a flat JSON array:

[3, 7, 1]

The file must contain ONLY the JSON array.

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. 3d ago First seen · 33 lines · 32 tokens per session scan A 7af1a05be873

Subscribe to this mod's changes

claim-triage is an agent published in the GitHub repository MadGraphTeam/MadAgents (10 stars, last pushed 28d ago), licensed MIT. It adds 32 tokens to every session and 243 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-31.