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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/gonzalezpazmonica/pm-workspace/coherence-judge)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/coherence-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/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.
<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/coherence-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/coherence-judge.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00777 |
| Opus 5 | $0.00010 | $0.00388 |
| Sonnet 5 | $0.00004 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00078 |
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 11d 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.
This is a copy
100% identical to coherence-judge — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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
- Arithmetic: totals sum correctly (sprint SP, hours, velocity deltas). When the report has tables with totals, verify math.
- Percentages: sum to ≤100 where appropriate; complementary percentages match (if "60% done", "remaining" should be "40%").
- Date ordering: start < end, timestamps in chronological order, "next sprint" > "current sprint".
- Entity consistency: same person/project referenced with same spelling throughout (not "María" in one section and "maria" in another).
- Claim consistency: section A says X, section B says ¬X — flag.
- Cross-references: "see section 3" — section 3 must exist.
- 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
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.
- 11d ago First seen · 91 lines · 19 tokens per session scan A 9eba477c05d2
coherence-judge is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 5d ago), 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. It is 100% identical to coherence-judge, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
quarto-critic
Adversarial QA agent that compares Quarto HTML against Beamer PDF benchmark. Produces harsh, actionable criticism. Does NOT edit files — read-only analysis only.
openwriter-enrichment-minion
Refresh stale OpenWriter loglines through exclusive canonical snapshot claims.
literature-extractor
Extracts literature Statements from papers for a survey. Reads PDFs, creates Statements with source="literature" and verification="pending", returns a structured report. Never registers theme tags, never creates Warrants or Claims.
chronology-builder
Isolated worker that reads case documents iteratively and extracts sourced timeline events (date, neutral fact, mandatory document+locus provenance, undisputed/alleged/contested status, party attribution). Deduplicates and cross-references across documents and languages. Emits events.json for the legal-chronology…
flow-documenter
Use this agent when you need to generate comprehensive, natural language documentation for a Power Automate flow from its JSON definition. This agent should be invoked when:\n\n- A user provides a flow.json file and requests documentation\n- A new flow has been created and needs to be documented\n- An existing flow…
ops-documentacao
Especialista em documentação interna estruturada (Notion, Confluence, GitBook, wikis) para PMEs aplicando framework Diátaxis (Procida), BPMN, ITIL v4, ISO 9001, RACI. Use proativamente quando o usuário (a) escrever SOP / procedimento operacional padrão com estrutura completa (id, owner, escopo, ferramentas, fluxo…