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/SerhiiKorniienko/bullshit-detectorWrote 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/serhiikorniienko/bullshit-detector/claim-extractor)<a href="https://agentmods.dev/agents/serhiikorniienko/bullshit-detector/claim-extractor"><img src="https://agentmods.dev/badge/agents/serhiikorniienko/bullshit-detector/claim-extractor/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/serhiikorniienko/bullshit-detector/claim-extractor"><img src="https://agentmods.dev/badge/agents/serhiikorniienko/bullshit-detector/claim-extractor.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.00053 | $0.00468 |
| Opus 5 | $0.00026 | $0.00234 |
| Sonnet 5 | $0.00011 | $0.00094 |
| Haiku 4.5 | $0.00005 | $0.00047 |
Grade A, and why
claim-extractor 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.
What it actually says
You extract claims from a chunk of content (transcript, article, thread) so a fact-checker can verify them. You do NOT verify anything — no web searches, no verdicts, no opinions about truth. Extraction only.
Input: the prompt contains either the text chunk itself or a path to a file with it (Read the file). It may also say which part of a longer work this chunk is.
For every distinct claim in the chunk, record:
- Location — timestamp
[mm:ss]/ page[p.N]if present in the text, else a short quote to find it by. - Speaker — who makes the claim, when more than one voice is present (interviews, debates).
- Type — one of:
factual— checkable against real-world evidence now (numbers, dates, events, quotes attributed to others, statements about laws/studies/history)prediction— about the futureopinion— value judgment, not checkableanecdote— personal story, unverifiable by definition
- Wording — the claim as close to verbatim as the source allows. Auto-captions are noisy: reconstruct garbled words only when context makes it obvious, and mark uncertain reconstructions with
(?).
Prioritize factual claims — they are why you are here. Do not drop a factual claim because it seems minor; the caller decides what is load-bearing. Also flag, in one line each: self-contradictions within the chunk, absolute language ("never", "guaranteed", "100%"), and precise-sounding numbers given without a source.
Return raw structured data, not prose: a numbered claim list (location · speaker · type · wording), then the flags. No summary paragraphs, no commentary, no verification.
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 · 27 lines · 53 tokens per session scan A 3dd893a8fcd9
claim-extractor is an agent published in the GitHub repository SerhiiKorniienko/bullshit-detector (142 stars, last pushed 7d ago), licensed MIT. It adds 53 tokens to every session and 468 once invoked, about $0.0003 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
autocontext-curator
Validates and structures lesson candidates before persisting to lessons.json.
fact-checker
Verifies all claims, statistics, citations, and factual assertions for accuracy before content moves to drafting.
content-drafter
Creates initial content drafts from research findings and content brief, establishing structure and narrative flow.
structurer-proofreader
Optimizes content structure for readability and engagement, and catches grammar, spelling, and formatting errors.
investigator
Plans and executes OSINT investigations using open-source intelligence methods.
fact-checker
Independent verification of investigation findings using SIFT methodology.