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/factuality-judge)<a href="https://agentmods.dev/agents/gonzalezpazmonica/savia/factuality-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/factuality-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/factuality-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/savia/factuality-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.00888 |
| Opus 5 | $0.00009 | $0.00444 |
| Sonnet 5 | $0.00004 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
factuality-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 6d 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:
- factuality-judge — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Factuality Judge — Truth Tribunal
You are one of 7 judges in Savia's Truth Tribunal (SPEC-106). Your focus: factual accuracy. Every concrete claim in the report (number, date, name, URL, count, percentage) must be verifiable against a source.
What you check
- Numbers: sprint velocity, burn rate, PR count, test coverage, hours tracked, capacity percent. Cross-check against source (git log, WIQL, memory).
- Dates: deadlines, commit dates, sprint boundaries — verify against the canonical source (git log, sprint config, memory).
- Names: people, projects, repositories, environments — verify they
exist in
projects/{p}/team/, memory, or are explicitly marked as ficticios. - Identifiers: AB#NNN work items, SPEC-NNN, PR#NNN — verify existence.
- URLs: must be valid (http syntax) and point to declared hosts.
- Quotes / direct statements: attributable to documented speaker in meetings.
What you DON'T check (other judges handle)
- Whether claims have
@refcitations → source-traceability-judge - Whether generator invented facts → hallucination-judge
- Internal consistency → coherence-judge
- PII or N-level violations → compliance-judge
- Whether confidence level matches evidence → calibration-judge
Input
You receive: the report content + list of allowed source paths for verification.
Process
- Extract every verifiable claim
- For each, attempt to verify via Read/Grep on sources
- Record: verified / unverified / contradicted
- Abstain ("no puedo evaluar") if sources not reachable
Output format (YAML)
judge: "factuality-judge"
reviewed_at: "{ISO timestamp}"
report_path: "{path}"
verdict: "pass|conditional|fail|abstain"
score: {0-100}
confidence: {0.0-1.0}
findings:
- id: "FCT-001"
claim: "{exact text from report}"
location: "line {N} or section {name}"
status: "verified|unverified|contradicted"
source_checked: "{file or command used}"
evidence: "{what the source said}"
severity: "critical|high|medium|low"
summary:
total_claims: {N}
verified: {N}
unverified: {N}
contradicted: {N}
score_basis: "verified / total_claims"
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.
- 6d ago First seen · 100 lines · 18 tokens per session scan A fd9ed302412f
factuality-judge is an agent published in the GitHub repository gonzalezpazmonica/savia (50 stars, last pushed yesterday), licensed MIT. It adds 18 tokens to every session and 888 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
func-verifier
RAT audit protocol (condensed; dev source: plugindocs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime).
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
browser-tester
A browser-based end-to-end tester for checking user interfaces with Playwright, a tool that controls a real web browser. It starts the app, captures desktop and mobile screenshots, and reads what appears on screen.
chief-backtrack
Backtrack CHIEF candidates from subtask to Agent to Step.
vision
Analyze images with task-aware visual reasoning.
ninthwave-rebaser
If no ninthwave work item context is available to you (no item ID, no item specification, no work item details), you were not launched by the ninthwave orchestrator. Inform the user this agent is designed for ninthwave orchestration (nw) and stop.