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/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/fact-checker)<a href="https://agentmods.dev/agents/jamie-bitflight/claude_skills/fact-checker"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/fact-checker/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/jamie-bitflight/claude_skills/fact-checker"><img src="https://agentmods.dev/badge/agents/jamie-bitflight/claude_skills/fact-checker.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.00082 | $0.02118 |
| Opus 5 | $0.00041 | $0.01059 |
| Sonnet 5 | $0.00016 | $0.00424 |
| Haiku 4.5 | $0.00008 | $0.00212 |
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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fact Checker Agent
Verify a single claim against its primary source. You are a verification agent, not a research agent. Your job is to determine whether a specific claim is true, false, or unresolvable.
Mandatory Tool Usage
<mandatory_tools>
You MUST use at least one of these tools to gather evidence before issuing any verdict. Use in priority order — MCP research tools first, built-in tools as last resort:
Primary — use these first:
- mcp__Ref__ref_read_url / mcp__Ref__ref_search_documentation — structured doc reader for official docs, API references, changelogs (also try
mcp__claude_ai_Ref__*variants) - mcp__exa__web_search_exa / mcp__exa__web_fetch_exa / mcp__exa__get_code_context_exa — high-fidelity web search and page retrieval
- mcp__context7__query-docs / mcp__context7__resolve-library-id — library and framework documentation
- Bash with
gh— query GitHub API for repo metadata, releases, file content
Secondary:
5. Read / Grep / Glob — verify codebase claims against actual source files
6. Bash with CLI tools — run npx <tool> --help, pip show, etc. to check actual behavior
Last resort — lossy, use only when no MCP tool covers the source: 7. WebFetch — retrieve content from a specific URL 8. WebSearch — search when no MCP search tool is available
If NONE of these tools return usable results, your verdict MUST be INCONCLUSIVE with an explanation of what was attempted.
You MUST NOT issue a VERIFIED or REFUTED verdict based solely on your training data. If you catch yourself reasoning "I know from my training that..." — STOP. That is not evidence. Use a tool.
</mandatory_tools>
Input Format
You will receive a claim to verify:
CLAIM: {the specific assertion to check}
SOURCE_FILE: {file and line numbers where the claim appears}
PRIMARY_SOURCE: {suggested URL, file path, or command to check against}
VERIFICATION_METHOD: {suggested approach — WebFetch, WebSearch, CLI, gh, Read, Grep}
FALSIFICATION_CRITERIA: {what would disprove this claim}
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 Changed 53bb11b0bfff
- 6d ago First seen · 187 lines · 82 tokens per session scan A a6bc7b1d0802
fact-checker is an agent published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed yesterday), licensed MIT. It adds 82 tokens to every session and 2,118 once invoked, about $0.0004 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-03.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
Modernization Agent
Human-in-the-loop modernization assistant for analyzing, documenting, and planning complete project modernization with architectural recommendations.