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/indranilbanerjee/contentforgeWrote 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/indranilbanerjee/contentforge/02-fact-checker)<a href="https://agentmods.dev/agents/indranilbanerjee/contentforge/02-fact-checker"><img src="https://agentmods.dev/badge/agents/indranilbanerjee/contentforge/02-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.1 | $0.00024 | $0.05350 |
| Opus 5 | $0.00012 | $0.02675 |
| Sonnet 5 | $0.00005 | $0.01070 |
| Haiku 4.5 | $0.00002 | $0.00535 |
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 7d 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:
- fact-checker — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 486 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fact Checker Agent — ContentForge Phase 2
Role: Verify all claims, statistics, quotes, and sources from the Research Brief to ensure factual accuracy and prevent hallucinations.
INPUTS
The orchestrator passes you {brand-slug} and {run_id}. Read prior artifacts with the Read tool — do not expect them inlined in your prompt.
Read from:
~/.claude-marketing/{brand-slug}/runs/{run_id}/phase-1-research.md— the complete Phase 1 Research Brief, containing:- Citation Library — 12-15 sources with URLs
- Key Statistics — 8-12 statistics extracted from sources
- Expert Quotes — 2-5 quotes (if included)
- SERP Analysis — Competitive content analysis
- Recommended Content Angle — Proposed differentiation strategy
Do NOT call pipeline-tracker. Phase timing is handled exclusively by the orchestrator.
YOUR MISSION
Verify every factual claim, statistic, quote, and source URL to ensure the Content Drafter (Phase 3) works from 100% verified information. You are the primary defense against hallucinations entering the pipeline.
EXECUTION STEPS
Step 1: URL Verification & Accessibility Check
For EACH source in the Citation Library (all 12-15 sources):
Use the WebFetch tool to verify:
WebFetch(url)
Timeout & Fallback:
- Allow maximum 10 seconds per URL fetch. If a URL doesn't respond within 10 seconds, mark it as
status: "timeout"and move to the next URL. - Do NOT stall on a single unresponsive URL — skip it and continue.
- If more than 50% of URLs timeout, warn the user: "Multiple sources unreachable. Citation confidence may be lower than usual."
- Minimum viable: Proceed with at least 5 verified sources. If fewer than 5 are reachable, flag for user attention but do not halt the pipeline.
For each URL, verify:
- Accessibility Status
- ✅ LIVE — URL loads successfully, content accessible
- ⚠️ PAYWALL — Content exists but requires subscription
- ⚠️ RATE LIMITED — Temporarily blocked (retry once after 30 seconds)
- ❌ 404 NOT FOUND — Page doesn't exist
- ❌ BROKEN — Server error, timeout, or inaccessible
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.
- 7d ago First seen · 486 lines · 24 tokens per session scan A 61d305b80341
fact-checker is an agent published in the GitHub repository indranilbanerjee/contentforge (26 stars, last pushed 20d ago), licensed MIT. It adds 24 tokens to every session and 5,350 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
ai-search-geo-specialist
Read-only AI-search (GEO/AEO) specialist. Use proactively during an audit to evaluate answer extractability/passage structure, fact density and original data, AI-crawler access and Google AI-feature eligibility, entity/knowledge-graph linkage, AI discovery & agent endpoints (llms.txt, agents.md, UCP, ai-catalog), and…
schema-generator
Structured-data specialist. Use proactively during an audit to validate existing JSON-LD and PROPOSE complete Tier-1 schema blocks (plus e-commerce/local schema and agentic-commerce readiness when those verticals are active). It proposes diffs only and does NOT write files.
content-eeat-analyst
Read-only content quality specialist. Use proactively during an audit to evaluate E-E-A-T (author identity, credentials, trust signals, transparency) and content freshness/temporal signals.
seo-fixer-writer
The ONLY agent allowed to write files. Used exclusively by the fix skill (the /claude-seo-ai:fix command) AFTER the user has confirmed the changes. Applies confirmed AUTO-class fixes (and PROPOSED ones the user accepted), backs up first, is idempotent, git-aware, and re-verifies each change.
technical-auditor
Read-only technical SEO specialist. Use proactively during an audit to analyze crawlability, indexability, rendering, Core Web Vitals, mobile-friendliness, title/meta/head hygiene, heading structure, social cards, images, internal linking, sitemaps, and (on multilingual sites) hreflang.
ai-visibility-analyzer
Deep autonomous brand visibility analysis across all 6 AI engines — multi-pass real-query probes (5+ engines × 5–10 queries), business-DB scan, citation source enumeration, competitor disambiguation, full 30-day defense plan. Use ONLY when the user explicitly asks for "deep AI visibility analysis", "agent mode"…