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 artem-from-ua/claude-plugins --skill fresh-guides-verifygit clone --depth 1 https://github.com/artem-from-ua/claude-pluginsWrote 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/artem-from-ua/claude-plugins/fresh-guides-verify)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/fresh-guides-verify"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/fresh-guides-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.
<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/fresh-guides-verify"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/fresh-guides-verify.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.00078 | $0.00967 |
| Opus 5 | $0.00039 | $0.00483 |
| Sonnet 5 | $0.00016 | $0.00193 |
| Haiku 4.5 | $0.00008 | $0.00097 |
Grade A, and why
fresh-guides-verify 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 12d 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.
Fresh Guides — Verification Procedure
A technology on the user's fresh-guides watchlist was detected in the conversation. Follow this procedure BEFORE giving version-specific advice.
Steps
1. Identify the matched technology
Find the matching entry in the watchlist (injected by SessionStart). Note:
- The technology
namefrom the watchlist - The configured
docsURLs
2. Determine the current version
Before giving any advice, establish which version of the technology is in use:
- Check the project — look for version pins in lockfiles, config files, or dependency manifests (e.g.,
terraform { required_version },package.json,go.mod,.tool-versions, DockerfileFROMtags, provider version constraints). - Check runtime — if the tool is available locally, run its version command (e.g.,
terraform version,kubectl version --client,aws --version). - If neither works — ask the user: "Which version of are you using?" Do NOT assume "latest" — the user may be on an older version with different behavior.
All subsequent verification MUST target the specific version identified in this step.
3. Determine what needs verification
Identify the specific claim, API, behavior, config syntax, or default that could have changed since training cutoff. Not everything needs verification:
Verify: API signatures, default values, config syntax, deprecations, new features, pricing, limits, CLI flags, provider arguments, service quotas.
Skip verification: General concepts, design patterns, architectural principles, well-established fundamentals that don't change across versions.
4. Fetch official documentation
Use WebFetch on the configured doc URLs to find information about the specific topic:
- Try the most specific doc URL first (e.g., API reference > general docs)
- When the official docs have versioned URLs (e.g.,
/v1.6.x/,/latest/), target the URL for the user's specific version — not "latest" - If the page is too large or doesn't contain the answer, use
WebSearchwith a targeted query:"<technology> <version> <specific feature/API> official documentation" - For release notes / changelogs, search for the specific version or recent 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.
- 12d ago First seen · 88 lines · 78 tokens per session scan A 9241e56a446f
fresh-guides-verify is a skill published in the GitHub repository artem-from-ua/claude-plugins (11 stars, last pushed 3d ago), licensed MIT. It adds 78 tokens to every session and 967 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-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…
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…
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…