A freshness checker for claims that can become outdated, such as software versions, end-of-life dates, package releases, container tags, and AI model availability. It uses primary sources and can run automatically before file edits or manually for a topic.

Use it to check current versions, support dates, dependency status, GitHub Action references, Kubernetes API versions, image tags, or model deprecations.

It reminds you to verify time-sensitive technical facts instead of relying on old information.

verify — Skill for Claude Code by raisedadead/claude-code-plugins

Install

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.

Any agent

npx skills add raisedadead/claude-code-plugins --skill verify

Clone the repo

git clone --depth 1 https://github.com/raisedadead/claude-code-plugins

Made for: Claude Code.

Or install dossier, the plugin that ships this one along with the rest of its 8 skills, 2 agents.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/verify/github.svg)](https://agentmods.dev/skills/raisedadead/claude-code-plugins/verify)

Your own site

<a href="https://agentmods.dev/skills/raisedadead/claude-code-plugins/verify"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/verify/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/raisedadead/claude-code-plugins/verify"><img src="https://agentmods.dev/badge/skills/raisedadead/claude-code-plugins/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 130 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,733 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00130	$0.01733
Opus 5.5	$0.00052	$0.00693
Sonnet 5.5	$0.00026	$0.00347
Haiku 4.5	$0.00013	$0.00173

Measured 14d ago against content hash 95c4212a8e5f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

verify scanned grade A with 1 finding 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 14d 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

- JSON APIs: `Bash` + `curl -s <url>`, so you read raw JSON. `WebFetch` summarises JSON, and a summary can hallucinate.

plugins/dossier/skills/verify/SKILL.md · 98 lines

How it starts

The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.

ds:verify — empirical freshness check

Two surfaces, one rule: read the primary source's raw bytes.

Surface 1 — PreToolUse hook (auto)

Wired in the mod, hooks/register.ts. Fires on Edit | Write, and only in a repo that has a .scratchpad/dossier/ directory — elsewhere it does not scan. Scans content against the pattern registry in engine/verify.ts and the authority catalog in engine/verify-authorities.ts (140+ aliases, 34 Docker images, 31 AI models). Covers language/runtime/OS/distro/database EOL, container-image EOL, GitHub Action SHA pinning, k8s deprecated apiVersions, npm/PyPI/Cargo/RubyGems/Go-mod outdated packages, and AI-model deprecation. Full coverage matrix + per-source cheatsheet → references/authorities.md.

Non-blocking by design — a finding is additionalContext only. Per-session dedup, held in the mod; a hot reload of the plugin resets it. The hook reads the cache only and never fetches. Operator escape: # verify-skip: <ruleName> anywhere in the written content.

Cache at <project root>/.scratchpad/.verify-cache/ (24h TTL on registries, 30d on resolved SHAs). Offline = silent skip.

Surface 2 — `/dossier:verify [<topic>]` (manual, generic)

No pattern lock-in: the model classifies an arbitrary freshness claim and routes it to the right primary source.

Steps

Identify claims. From $ARGUMENTS when provided, else every freshness-sensitive claim in the previous assistant message. Freshness-sensitive = the answer could plausibly have changed since the training cutoff.
Classify each claim into one of these buckets:
- Version / LTS / EOL of language, OS, distro, database, runtime → endoflife.date/api/v1/products/<slug>
- Package latest → ecosystem registry (npm/PyPI/crates/RubyGems/Hex/Packagist/Go proxy/Maven Central/Homebrew)
- GitHub release / tag / SHA → api.github.com/repos/<owner>/<repo>/releases/latest or /git/refs/tags/<tag>
- CLI flag / subcommand → vendor docs (search official site)
- API endpoint / schema → vendor docs / OpenAPI spec
- AI model identifier → vendor deprecation page (OpenAI/Anthropic/Google/Mistral/Meta)
- Framework / library API → official docs (search) or release notes
- License / SPDX identifier → spdx.org/licenses/
- Standard / RFC → ietf.org / w3.org
- Anything else freshness-sensitive → WebSearch first, then WebFetch the top primary source.
Query the authority.
- JSON APIs: Bash + curl -s <url>, so you read raw JSON. WebFetch summarises JSON, and a summary can hallucinate.
- HTML docs: WebSearch then WebFetch, quoting the exact text you compared against.
- GitHub: gh api <path> over WebFetch on github.com.
Compare exact field values. Pull the specific field (releases[].name, info.version, crate.newest_version, …) and compare it against the claim's literal value. The comparison is field-to-value, not prose-to-impression.
Render verdict table.

Read the full file on GitHub · 98 lines

Files

What ships with it

1 file 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.

references/authorities.md 6.1 KB

Changes

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.

14d ago Changed · -1 lines 95c4212a8e5f
18d ago Changed · -3 tokens per session c9f0087d2a6b
1mo ago Changed 390de5f01d83
1mo ago Changed effe24b9be8a
1mo ago First seen · 99 lines · 133 tokens per session scan A ad2c50fc7bae

Subscribe to this mod's changes

verify is a skill published in the GitHub repository raisedadead/claude-code-plugins (3 stars, last pushed today), licensed ISC. It adds 130 tokens to every session and 1,733 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Research

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…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 83 tokens

verify