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 jqaisystems/jqai-ai-skills --skill verify-public-claimsgit clone --depth 1 https://github.com/jqaisystems/jqai-ai-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/skills/jqaisystems/jqai-ai-skills/verify-public-claims)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/verify-public-claims"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/verify-public-claims/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/jqaisystems/jqai-ai-skills/verify-public-claims"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/verify-public-claims.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.00065 | $0.00612 |
| Opus 5.5 | $0.00026 | $0.00245 |
| Sonnet 5.5 | $0.00013 | $0.00122 |
| Haiku 4.5 | $0.00006 | $0.00061 |
Grade A, and why
verify-public-claims 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 1mo 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify Public Claims
Turn public-facing statements into a traceable claim ledger, then revise the copy so every material assertion matches the available evidence.
1. Establish the review contract
- Confirm the copy, intended audience, publication surface, relevant date, and evidence supplied by the user.
- Identify whether the request covers factual accuracy, freshness, wording strength, source quality, or all four.
- Browse current public sources when a claim may have changed or the user asks for current verification.
- Use only public sources or evidence the user has approved for this review.
- Do not treat inaccessible, login-only, or missing material as verified.
2. Build the claim ledger
- Use assets/claim-ledger-template.md.
- Split compound sentences when their parts need different evidence.
- Record the exact claim, source, publication date, event date when different, verification date, evidence excerpt or paraphrase, and intended rewrite.
- Read references/evidence-statuses.md before assigning a status.
- Focus on claims that affect trust, decisions, eligibility, scope, performance, recency, identity, or attribution.
3. Classify each claim
Use exactly one primary status:
supported: direct, relevant, sufficiently current evidence supports the wordingqualified: the core is supported, but the wording needs a limit, date, scope, or attributioninference: the conclusion is reasonable but is not stated directly by the evidenceunsupported: no adequate evidence supports the material claimstale: the evidence may once have supported the claim but is too old for present-tense use
When sources conflict, preserve the conflict in the ledger and prefer the most direct authoritative current source. Do not resolve uncertainty by averaging, guessing, or silently choosing the most favorable version.
4. Rewrite to the evidence level
- Keep supported claims precise.
- Add the required scope, date, source, or attribution to qualified claims.
- Label inference as analysis, interpretation, estimate, or recommendation.
- Remove unsupported claims or replace them with narrower wording that the evidence supports.
- Update stale claims only when a current source is available; otherwise hold or date the wording.
- Never invent citations, metrics, testimonials, dates, credentials, customers, outcomes, or source access.
What ships with it
3 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.
- 1mo ago First seen · 50 lines · 65 tokens per session scan A 9b52cfe8ceb4
verify-public-claims is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 13d ago), licensed MIT. It adds 65 tokens to every session and 612 once invoked, about $0.0003 per session on Opus 5.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-31.
Other skills, from other repositories
reins
Drive the user's real, logged-in browser from the shell via the reins CLI. Because it's their actual browser, every site is already authenticated — so you can scrape behind logins, read cookies/tokens/localStorage, watch and replay live API traffic, call a site's own API as the signed-in user, and…
baoyu-comic
A tool for creating original educational comics that explain knowledge or ideas through multiple illustrated panels. It supports different art styles and tones and can create several comics in one batch.
baoyu-diagram
Create professional, dark-themed SVG diagrams of any type — architecture diagrams, flowcharts, sequence diagrams, structural diagrams, mind maps, timelines, illustrative/conceptual diagrams, and more. Use this skill whenever the user asks for any kind of technical or conceptual diagram, visualization of a system…
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…
spring-boot-team-harness
Use when a team wants every developer's coding agent (Claude Code or Codex) to follow the same rules on a Maven Spring Boot 4 repository: setting up AGENTS.md, guardrails, shared agent settings, or build and CI checks that agents must pass before code merges. It adds ./mvnw verify gates that fail on null-safety bugs…
agent-wiki
Incremental LLM-friendly wiki generator for Obsidian note vaults. Use when: (1) Building wiki from notes, (2) Ingesting notes to wiki, (3) Obsidian LLM wiki, (4) Incremental knowledge base management. Triggers: 'build wiki from notes', 'ingest notes to wiki', 'Obsidian LLM wiki', 'incremental knowledge base'.