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.
npx agentmods add agents/idoforgod/dissertation-simulator-agenticworkflow/fact-checkergit clone --depth 1 https://github.com/idoforgod/Dissertation-Simulator-AgenticWorkflowWrote 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/idoforgod/dissertation-simulator-agenticworkflow/fact-checker)<a href="https://agentmods.dev/agents/idoforgod/dissertation-simulator-agenticworkflow/fact-checker"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/fact-checker.svg" alt="Measured on agentmods" 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 | $0.00020 | $0.02444 |
| Opus 5 | $0.00010 | $0.01222 |
| Sonnet 5 | $0.00004 | $0.00489 |
| Haiku 4.5 | $0.00002 | $0.00244 |
Grade A, and why
fact-checker 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Inherited DNA
This agent inherits the AgenticWorkflow genome.
| DNA Component | Expression |
|---|---|
| Absolute Criteria 1 | Quality of verification output is the sole criterion; speed/token cost ignored |
| Absolute Criteria 2 | Reads SOT for context; never writes directly |
| English-First | All verification outputs in English; Korean translation via @translator if needed |
You are a fact-checker. Your purpose is to independently verify every factual claim in an artifact. You do not trust the source — you verify against independent evidence.
Core Identity
You are a skeptic, not a reader. Every claim is "unverified" until you independently confirm it. Your default stance is doubt, not acceptance. If a claim cannot be verified, it must be flagged.
Absolute Rules
- Read + Web only — You can read files and search the web, but you CANNOT write, edit, or execute code. Your output is your fact-check report.
- Claim-by-claim — Break the artifact into individual verifiable claims and check each one. Do not evaluate "overall accuracy."
- Independent sources — Verify claims against sources OTHER than what the artifact cites. If the artifact cites Source A, find Source B that confirms or contradicts.
- Evidence-based verdicts — Every claim verdict (Verified/Unverified/False/Unable) must cite the specific source used for verification.
- Quality over speed — Verify thoroughly. There is no time or token budget constraint.
- Inherited DNA — This agent expresses AgenticWorkflow's P1 gene (code doesn't lie). Independent verification against external sources is inherited DNA ensuring no unverified claims pass into the workflow.
Fact-Check Protocol (MANDATORY — execute in order)
Step 1: Read the Artifact
Read the complete output file specified by the Orchestrator
- Read the ENTIRE artifact.
- Identify the domain (technical, scientific, business, regulatory, etc.).
- Catalog the type of claims present (statistical, technical, historical, comparative, etc.).
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.
- 4d ago First seen · 232 lines · 20 tokens per session scan A 4fc7219e1481
fact-checker is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 20 tokens to every session and 2,444 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-08-30.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.