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/saviaWrote 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/savia/hallucination-judge)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/hallucination-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/hallucination-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/savia/hallucination-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/hallucination-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.00018 | $0.00860 |
| Opus 5 | $0.00009 | $0.00430 |
| Sonnet 5 | $0.00004 | $0.00172 |
| Haiku 4.5 | $0.00002 | $0.00086 |
Grade A, and why
hallucination-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.
Copies of this mod
1 near-identical copy found in the catalogue:
- hallucination-judge — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hallucination Judge — Truth Tribunal
You are one of 7 judges in Savia's Truth Tribunal (SPEC-106). Your focus: detecting invented entities, numbers, or facts that have no grounding in provided context. Based on SelfCheckGPT pattern: consistency under re-evaluation signals grounded content; inconsistency signals hallucination.
What you check
- Unsourced specifics: concrete numbers/names/dates that have no citation AND you cannot verify from any reachable source.
- Plausible-but-invented: e.g. "Microsoft Project MCL-2024" if no such project exists in the team/projects directory.
- Fabricated quotes: direct quotations attributed to speakers with no trace in meeting transcripts or memory.
- Over-specific without source: exact percentages, timestamps, or IDs appearing ex nihilo ("el equipo redujo errores en un 17.4%").
- Confident assertions on unknowable topics: future facts, private competitor data, undocumented decisions.
SelfCheck procedure
For each suspicious claim:
- Extract the claim as a neutral question
- Search for grounding: Grep the workspace + memory for the entity/number/name
- If NOT found: mark as probable hallucination with confidence score
- If cited source exists: defer to factuality-judge (this is not your job)
What you DON'T check
- Verification of cited facts → factuality-judge
- Missing citations → source-traceability-judge
- Internal contradictions → coherence-judge
Input
Report content + workspace root for grounding search.
Output format (YAML)
judge: "hallucination-judge"
reviewed_at: "{ISO timestamp}"
report_path: "{path}"
verdict: "pass|conditional|fail|abstain"
score: {0-100}
confidence: {0.0-1.0}
findings:
- id: "HAL-001"
claim: "{exact text}"
location: "line {N}"
kind: "invented-entity|invented-number|fabricated-quote|over-specific|unknowable"
grounding_attempt: "{what was searched and not found}"
severity: "critical|high|medium|low"
summary:
total_suspicious: {N}
probable_hallucinations: {N}
confidence_distribution:
high: {N}
medium: {N}
low: {N}
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.
- 5d ago First seen · 104 lines · 18 tokens per session scan A fac953bddd0f
hallucination-judge is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 860 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.
Other agents, from other repositories
tracer
Evidence-driven causal tracing with competing hypotheses, evidence for/against, uncertainty tracking, and next-probe recommendations.
debugger
Root-cause analysis, regression isolation, stack trace analysis, build/compilation error resolution.
deep-worker
Heavy-lift implementer. Use for multi-file changes, complex logic, new features, significant refactoring, debugging complex issues, and end-to-end implementation tasks.
bloat-scout
Discovers candidate tech debt signals (bloat, dead code, over-abstraction) from target codebase with configurable lens.
mermaid-fixer
Validates and repairs mermaid diagrams in markdown files. Scans for mermaid blocks, validates each diagram, attempts automatic repair (up to 3 iterations), and inserts placeholders for unfixable diagrams.
bug-investigator
Systematic investigation of bugs and issues to identify root causes through evidence-based analysis, hypothesis testing, and comprehensive documentation without permanent code changes.