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-updategit 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-update)<a href="https://agentmods.dev/skills/artem-from-ua/claude-plugins/fresh-guides-update"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/fresh-guides-update/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-update"><img src="https://agentmods.dev/badge/skills/artem-from-ua/claude-plugins/fresh-guides-update.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.00538 |
| Opus 5 | $0.00039 | $0.00269 |
| Sonnet 5 | $0.00016 | $0.00108 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
fresh-guides-update 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.
What it actually says
Fresh Guides Update
Quickly update a single aspect of the fresh-guides watchlist.
Config Resolution
Determine which config file to update:
- If
.claude-plugin/fresh-guides.jsonexists → update project config - Else if
~/.claude/fresh-guides.jsonexists → update global config - Else → create global config from template, then apply update
Supported Operations
Add technology
Usage: /fresh-guides-update add <name> <url>
Steps:
- Read config file.
- Check if
<name>already exists in watchlist (case-insensitive). If so, add the URL to itsdocsarray instead. - If new, append
{ "name": "<name>", "docs": ["<url>"] }to watchlist. - Write the updated config.
- Confirm: "Added to watchlist with doc URL: . Restart session for changes to take effect."
Remove technology
Usage: /fresh-guides-update remove <name>
Steps:
- Read config file.
- Remove the entry matching
<name>(case-insensitive) from watchlist. - Write the updated config.
- Confirm: "Removed from watchlist."
- If not found: " is not on the watchlist."
Add URL to existing technology
Usage: /fresh-guides-update url <name> <url>
Steps:
- Read config file.
- Find the entry matching
<name>(case-insensitive). - Append
<url>to itsdocsarray (skip if already present). - Write the updated config.
- Confirm: "Added doc URL for : ."
- If not found: " is not on the watchlist. Use
/fresh-guides-update add <name> <url>to add it."
Error Handling
- No arguments → show usage examples for all operations
- Config file missing → create from template, then apply update
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 · 62 lines · 78 tokens per session scan A a6c67b4401f6
fresh-guides-update 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 538 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…