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 adamlinscott/claude-skills --skill check-skill-updatesgit clone --depth 1 https://github.com/adamlinscott/claude-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/adamlinscott/claude-skills/check-skill-updates)<a href="https://agentmods.dev/skills/adamlinscott/claude-skills/check-skill-updates"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/check-skill-updates/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/adamlinscott/claude-skills/check-skill-updates"><img src="https://agentmods.dev/badge/skills/adamlinscott/claude-skills/check-skill-updates.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.00133 | $0.00914 |
| Opus 5 | $0.00067 | $0.00457 |
| Sonnet 5 | $0.00027 | $0.00183 |
| Haiku 4.5 | $0.00013 | $0.00091 |
Grade A, and why
check-skill-updates 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
check-skill-updates
Say nothing unless there is something to say. This skill exists to mention a waiting update once, at a moment when the user is not busy — and to be invisible the rest of the time.
Run it
node <repo>/tools/freshness/check.mjs
<repo> is the clone the skills are linked from. Resolve it from this file's real path, not
from the working directory: ~/.claude/skills/check-skill-updates is a link, so its target's
../../tools/freshness/check.mjs is the script. The working directory is whatever the user
happens to be editing, which is usually a different repo entirely.
The script prints one line of JSON and nothing else. Flags: --force (the user asked directly,
ignore the rate limit), --update (pull and re-link), --decline (remember this was turned down).
What each verdict means
| Verdict | What you say |
|---|---|
fresh |
Nothing. Silence is the correct output. |
too-soon |
Nothing. Already checked within the day. |
offline |
Nothing. A failed fetch is not the user's problem to hear about. |
not-installed |
Nothing, unless the user asked directly — then say the clone could not be found. |
unsafe |
Nothing, unless the user asked directly — then say the clone is on <branch> or has uncommitted changes, so it is not safe to pull for them. |
behind |
One line. See below. |
updated |
One line: what was applied. If refreshed is false, say the pull worked but the re-link did not, and name node <repo>/install.mjs --refresh. |
When the user invoked this skill directly, report every verdict plainly — being asked a question
is licence to answer it. When another skill called you, only behind earns any words at all.
Mentioning an update
One line, at the very end of whatever the calling skill was already saying, never in the middle:
Skills update available — 3 commits behind (
feat(are-we-done): add close-out gate). Update now?
Then honour the answer:
- Yes → run with
--update, then say in one line what was applied. The pull is safe mid-session: it changes the text of skills you already have, adds and removes nothing, and anything already running finishes on the version it started with. - No → run with
--declineand drop it. That version is never raised again, however long it sits there. Do not re-ask tomorrow; the answer has not expired. - No answer → drop it. An ignored offer is a no.
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 · 66 lines · 133 tokens per session scan A 581c1f8f543e
check-skill-updates is a skill published in the GitHub repository adamlinscott/claude-skills (3 stars, last pushed 10d ago), licensed MIT. It adds 133 tokens to every session and 914 once invoked, about $0.0007 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
implement
Use in the Implement phase whenever writing or editing production Java code, or fixing a bug, in a Spring/Spring Boot project. Enforces test-first (red-green-refactor), executes the approved plan step by step, and honors the project's path-scoped tech-stack rules and the task's enforcement set. Preloaded into…
review
Use in the Review phase before claiming any Java/Spring task is complete, fixed, or passing. Spawns the auditor subagents that check the implementation against every applicable skill, rule, and memory item, runs the test suite for fresh evidence, and re-spawns for at most two fix rounds before reporting what survives.…
claudehut-workflow
Use at the start of every session and whenever beginning a coding task in a Java/Spring backend - establishes the ClaudeHut 7-phase agentic workflow, the complexity-tier routing that lets small tasks skip deliberation phases, and the laws that govern which skills and rules must fire. Injected at session start; also…
discover
Use as the FIRST phase of EVERY coding task, before brainstorming - grounds the work in the existing codebase (entry points, key types, structure) and proves whether something reusable already exists. Produces the reuse-scan artifact the write gate requires and the reuse DECISION (adopt / extend / new). Runs inline on…
write-plan
Use in the Plan phase after the spec is approved - dispatches the planner agent to draft the executable plan from the standard template (decision summary, T-xxx task breakdown with test-first + verify per task), gets the user's approval, records the plan (opening the write gate), and mirrors the breakdown into Claude…
brainstorm
Use to generate and weigh solution approaches for a problem, after discovery has grounded the context. Produces two or more genuinely distinct options scored on trade-offs, recommends one, and (for code tasks) assembles the enforcement set the rest of the workflow audits against. General-purpose ideation — works for…