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 skills add jezweb/vite-flare-starter --skill fact-checkgit clone --depth 1 https://github.com/jezweb/vite-flare-starterWrote 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/skills/jezweb/vite-flare-starter/fact-check)<a href="https://agentmods.dev/skills/jezweb/vite-flare-starter/fact-check"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/fact-check/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/skills/jezweb/vite-flare-starter/fact-check"><img src="https://agentmods.dev/badge/skills/jezweb/vite-flare-starter/fact-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.00457 |
| Opus 5 | $0.00018 | $0.00229 |
| Sonnet 5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
fact-check 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 10d 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
Fact Check
When to use
The user has stated a specific claim and wants to know if it's accurate. Examples:
- "Is it true that X?"
- "Fact-check this: ..."
- "Did Y actually happen?"
Steps
-
Identify the claim — extract the precise factual assertion. If the claim is fuzzy ("apparently X is good"), use
ask_questionsto nail down what specifically to verify. -
Search for primary sources — use
web_searchwith the claim phrased neutrally. Look for:- Official sources (government sites, academic papers, the organisation involved)
- Reputable journalism (major outlets with editorial standards)
- Primary data (statistics agencies, public records)
-
Avoid these as sole sources:
- Social media posts (use only as leads to follow up)
- Single-source blogs without citations
- Anything that quotes the claim back without independent verification
-
Cross-reference — find at least 2-3 independent sources. If they all trace back to one origin, you only have one source.
-
Report verdict — use
show_alertwith the appropriate type:success— Confirmed (multiple authoritative sources agree)warning— Partly true / context needederror— False (sources contradict the claim)info— Unverifiable (insufficient evidence either way)
-
Provide evidence — list the sources with what each one says. Use markdown links.
Style
- Be neutral. Avoid editorialising.
- Distinguish "X is false" from "I couldn't find evidence for X" — these are different.
- If the claim is partly true, be specific about which parts.
What not to do
- Don't trust a single source, even an authoritative one, for contested claims.
- Don't conflate "common knowledge" with verified fact.
- Don't fabricate confidence — uncertainty is a valid finding.
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.
- 10d ago First seen · 47 lines · 36 tokens per session scan A 851492bc19dd
fact-check is a skill published in the GitHub repository jezweb/vite-flare-starter (48 stars, last pushed 15d ago), licensed MIT. It adds 36 tokens to every session and 457 once invoked, about $0.0002 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…