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/factuality-judge)<a href="https://agentmods.dev/agents/gonzalezpazmonica/pm-workspace/factuality-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/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/pm-workspace/factuality-judge"><img src="https://agentmods.dev/badge/agents/gonzalezpazmonica/pm-workspace/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 12d 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 factuality-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 — 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.
- 12d ago First seen · 100 lines · 18 tokens per session scan A fd9ed302412f
factuality-judge is an agent published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), 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. It is 100% identical to factuality-judge, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
WinForms Expert
Support development of .NET (OOP) WinForms Designer compatible Apps.