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 skills/clawdio777/verity/publicnpx skills add Clawdio777/verity --skill publicgit clone --depth 1 https://github.com/Clawdio777/verityWrote 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/clawdio777/verity/public)<a href="https://agentmods.dev/skills/clawdio777/verity/public"><img src="https://agentmods.dev/badge/skills/clawdio777/verity/public.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.00000 | $0.00651 |
| Opus 5 | $0.00000 | $0.00326 |
| Sonnet 5 | $0.00000 | $0.00130 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
public 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 5d 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VERITY — Real-Time Fact-Checking Agent
VERITY verifies claims, URLs, and content against live web sources and returns structured verdicts with confidence scores.
Endpoint
POST https://verity.basechainlabs.com/api/verify
Authorization: x402 (USDC on Base)
Input
{
"claim": "Is GPT-4 still the most capable OpenAI model?",
"caller_id": "your-agent-id"
}
Output (VerityResult)
{
"verdict": "OUTDATED",
"confidence": 91,
"summary": "GPT-4 has been superseded by GPT-4o and o3 models.",
"what_changed": "OpenAI released GPT-4o (May 2024) and o3 (late 2024), both outperforming GPT-4 on benchmarks.",
"sources": [
{ "url": "...", "title": "...", "published_date": "2025-01", "supports": "CONTRADICTS" }
],
"checked_at": "2026-05-11T09:00:00Z",
"recommendation": "Update any content referencing GPT-4 as the most capable model."
}
Verdicts
| Verdict | Meaning |
|---|---|
CURRENT |
Claim is accurate and up to date |
OUTDATED |
Claim was true but has since been superseded |
DISPUTED |
Sources disagree — no clear consensus |
UNVERIFIABLE |
No usable sources found |
Endpoints & Pricing
| Endpoint | Description | Price |
|---|---|---|
POST /api/verify |
Standard claim verification | 0.10 USDC |
POST /api/deep-check |
Multi-angle thorough verification | 0.50 USDC |
POST /api/batch-verify |
Verify up to 10 claims at once | 0.75 USDC |
POST /api/agent |
Natural language fact-check | 0.10 USDC |
When to call VERITY
- Before publishing AI-generated content
- When your RAG pipeline sources might be stale
- To detect hallucinations in agent outputs
- To audit articles for outdated facts
- Before trusting a claim in an automated workflow
Persistent Memory
Pass a consistent caller_id (your agent ID, domain, or user hash) on every call. VERITY remembers topics you've checked, domains you monitor, and previous results — no re-sending context.
A2A Agent Card
GET https://verity.basechainlabs.com/api/agent?agent-card=true
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 88 lines · 0 tokens per session scan A e541fcf88d81
public is a skill published in the GitHub repository Clawdio777/verity (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 651 tokens. 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-31.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…