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 vosslab/vosslab-skills --skill docset-updatergit clone --depth 1 https://github.com/vosslab/vosslab-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/vosslab/vosslab-skills/docset-updater)<a href="https://agentmods.dev/skills/vosslab/vosslab-skills/docset-updater"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/docset-updater/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/vosslab/vosslab-skills/docset-updater"><img src="https://agentmods.dev/badge/skills/vosslab/vosslab-skills/docset-updater.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.00043 | $0.02110 |
| Opus 5 | $0.00022 | $0.01055 |
| Sonnet 5 | $0.00009 | $0.00422 |
| Haiku 4.5 | $0.00004 | $0.00211 |
Grade A, and why
docset-updater 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 10d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docset refresh
Overview
Bring the full documentation set current in one pass. This skill is an
orchestrator: it does not write architecture, install, usage, README.md, or
AGENTS.md content directly. It invokes the skill that owns each of those, in an
order where later skills can link into what earlier skills produced, then audits
the remaining docs/ files no per-doc skill owns.
Owned-doc routing
Each artifact has one owning skill. Dependencies follow ownership, so independent owners run together:
arch-docs->docs/CODE_ARCHITECTURE.md,docs/FILE_STRUCTURE.mdsetup-install-usage-docs->docs/USAGE.md,docs/INSTALL.mdsee-also-docs->docs/RELATED_PROJECTS.mdnews-release-docs->docs/RELEASE_HISTORY.md,docs/NEWS.mdreadme-docs->README.md(sole owner; links the core docs by convention, reserves the screenshot block)screenshot-docs->docs/screenshots/PNGs and the managed screenshot block insideREADME.mdanddocs/agents-md-fixer->AGENTS.md(bare-path pointers intodocs/*.md)
readme-docs owns all of README.md, so the doc producers create only their own
docs/ files and readme-docs writes every README link. With one owner per artifact,
the producers carry no write conflict and run together.
Dispatch by dependency edges, not a fixed barrier, so each owner starts as early as its inputs allow:
- Start immediately, no dependencies (one concurrent batch):
arch-docs,setup-install-usage-docs,see-also-docs,news-release-docs,readme-docs, and the remaining-docs audit (step 3). Each owns separate files, so they carry no write conflict.readme-docslinks the core docs (CODE_ARCHITECTURE,FILE_STRUCTURE,INSTALL,USAGE) by convention, so it runs alongside their producers; the final Markdown link check confirms the files exist. screenshot-docs<-readme-docs: start as soon asreadme-docshas reserved the screenshot block. It does not depend on the other producers, so it runs concurrently with the still-running batch (including the slowsee-also-docs) instead of waiting behind it.agents-md-fixer<- the doc producers and audit outputs: start once thedocs/*.mdfiles it links exist. It pointsAGENTS.mdat created paths, not prose, so it waits for file existence only, not content quality.
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.
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.
- 10d ago First seen · 163 lines · 43 tokens per session scan A f0999090f185
docset-updater is a skill published in the GitHub repository vosslab/vosslab-skills (2 stars, last pushed 14d ago), licensed MIT. It adds 43 tokens to every session and 2,110 once invoked, about $0.0002 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-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…
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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…