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 agentmods add skills/nexus-substrate/nexus-agents/version-checknpx skills add nexus-substrate/nexus-agents --skill version-checkgit clone --depth 1 https://github.com/nexus-substrate/nexus-agentsWrote 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/nexus-substrate/nexus-agents/version-check)<a href="https://agentmods.dev/skills/nexus-substrate/nexus-agents/version-check"><img src="https://agentmods.dev/badge/skills/nexus-substrate/nexus-agents/version-check.svg" alt="Measured on agentmods" 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 | $0.00038 | $0.00625 |
| Opus 5 | $0.00019 | $0.00313 |
| Sonnet 5 | $0.00008 | $0.00125 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
version-check 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 4d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Version Check Skill
Full documentation: CLAUDE.md
Quick Process
1. Check Package Status
npm view <package> version
npm view <package> deprecated
npm view <package> time.modified
npm view <package> engines
2. Evaluate Criteria
| Criterion | Pass | Fail |
|---|---|---|
| Deprecation | Not deprecated | Deprecated |
| Last update | Within 12 months | Over 12 months |
| Node version | Compatible with 22.x | Incompatible |
| Security | No advisories | Has advisories |
3. Run Security Audit
pnpm audit
Actions
If deprecated or outdated:
- Find replacement
- Create GitHub issue to track migration
- Document migration path
See CLAUDE.md for complete version verification protocol.
Anti-rationalization — Dependency choice
| Excuse | Counter |
|---|---|
| "It's the most-starred package" | Stars correlate with marketing, not maintenance. Check last-commit, open-issues-vs-resolved-rate, recent CVE response time. |
| "Latest version is fine, just install it" | Latest may be a 0.x with breaking changes, or a v2 alpha. Check stability marker — latest tag isn't always stable. |
| "I'll fix any issues that come up" | Cost of npm uninstall + replacement is a multiple of npm view upfront. Ten seconds of due diligence saves an afternoon. |
Red flags
- Dependency added via
npm install <name>without aversion-checkcite in the PR - Last commit > 12 months on a non-trivial dep
- Maintenance signal poor (open issues piling, no recent releases) but added anyway
- License incompatible with our MIT (e.g., AGPL, GPLv3 in CLI/library code)
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.
- 4d ago First seen · 74 lines · 38 tokens per session scan A bed49eab6e88
version-check is a skill published in the GitHub repository nexus-substrate/nexus-agents (18 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 625 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…