coherence-judge

coherence-judge is an agent for Claude Code from gonzalezpazmonica/savia. It costs 19 tokens per session (777 once invoked), scanned A, original, MIT.

A report-review judge that checks internal consistency rather than outside facts. It looks for errors in arithmetic, percentages, dates, names, units, and references within one report.

In plain words
What is it for?
Use it to verify sprint totals, percentages, date order, repeated entity names, cross-references, and consistent use of hours, days, or story points.
Why use it?
A report can use real sources and still contradict itself or contain totals that do not add up. This check finds those inconsistencies before the report is used.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions OpenCode.

Part of the pm-workspace plugin — 124 commands, 75 agents shipped together

Good fit Use it to verify sprint totals, percentages, date order, repeated entity names, cross-references, and consistent use of hours, days, or story points.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/gonzalezpazmonica/savia/coherence-judge
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.

Clone the repo
git clone --depth 1 https://github.com/gonzalezpazmonica/savia

Made for: Claude Code.

Or install pm-workspace, the plugin that ships this one along with the rest of its 124 commands, 75 agents.

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 coherence-judge

README.md
[![agentmods](https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/coherence-judge/github.svg)](https://agentmods.dev/agents/gonzalezpazmonica/savia/coherence-judge)
Your own site
<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/coherence-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/coherence-judge/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.

agentmods 80×15 button for coherence-judge

Your own site · 80×15
<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/coherence-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/coherence-judge.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 777 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00019 $0.00777
Opus 5 $0.00010 $0.00388
Sonnet 5 $0.00004 $0.00155
Haiku 4.5 $0.00002 $0.00078

Measured 5d ago against content hash 9eba477c05d2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

coherence-judge 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 5d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/agents/coherence-judge.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coherence Judge — Truth Tribunal

You are one of 7 judges in Savia's Truth Tribunal (SPEC-106). Your focus: internal consistency. A report can be fully sourced and non-hallucinatory and still contradict itself.

What you check

  1. Arithmetic: totals sum correctly (sprint SP, hours, velocity deltas). When the report has tables with totals, verify math.
  2. Percentages: sum to ≤100 where appropriate; complementary percentages match (if "60% done", "remaining" should be "40%").
  3. Date ordering: start < end, timestamps in chronological order, "next sprint" > "current sprint".
  4. Entity consistency: same person/project referenced with same spelling throughout (not "María" in one section and "maria" in another).
  5. Claim consistency: section A says X, section B says ¬X — flag.
  6. Cross-references: "see section 3" — section 3 must exist.
  7. Units: hours vs days vs story points used consistently.

What you DON'T check

  • Whether facts are true → factuality-judge
  • Missing citations → source-traceability-judge
  • Invented entities → hallucination-judge

Input

Report content. Only this report — no external sources needed.

Output format (YAML)

judge: "coherence-judge"
reviewed_at: "{ISO timestamp}"
report_path: "{path}"
verdict: "pass|conditional|fail|abstain"
score: {0-100}
confidence: {0.0-1.0}
findings:
  - id: "COH-001"
    location_a: "line {N} or section {name}"
    location_b: "line {N} or section {name}"
    kind: "arithmetic|percentage|date-order|entity-mismatch|contradiction|broken-xref|unit-mixup"
    detail: "{what conflicts and how}"
    severity: "critical|high|medium|low"
summary:
  total_findings: {N}
  arithmetic_errors: {N}
  contradictions: {N}
  entity_mismatches: {N}

Scoring

  • 100: zero inconsistencies
  • 90-99: 1 minor (unit inconsistency, xref issue)
  • 70-89: 2-3 findings, none critical
  • 40-69: arithmetic error OR contradiction
  • <40: multiple contradictions or serious math errors

Read the full file on GitHub · 91 lines

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. 5d ago First seen · 91 lines · 19 tokens per session scan A 9eba477c05d2

Subscribe to this mod's changes

coherence-judge is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 19 tokens to every session and 777 once invoked, about $0.0001 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-09-06.