upgrade-packages-js

upgrade-packages-js is a skill for Claude Code from georgekhananaev/claude-skills-vault. It costs 38 tokens per session (5,628 once invoked), scanned C, original, MIT.

A tool for upgrading JavaScript packages with checks for breaking changes and guidance for updating the code. It supports npm, pnpm, and Yarn, which are tools for installing project packages.

In plain words
What is it for?
It checks package managers, peer dependencies, Node.js and module compatibility, migration notes, tests, builds, lockfiles, and automated code migrations.
Why use it?
It reduces the risk of breaking a project when dependencies change, while keeping upgrades reviewable through Git.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit It checks package managers, peer dependencies, Node.js and module compatibility, migration notes, tests, builds, lockfiles, and automated code migrations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/georgekhananaev/claude-skills-vault/upgrade-packages-js
Install

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.

Any agent
npx skills add georgekhananaev/claude-skills-vault --skill upgrade-packages-js
Clone the repo
git clone --depth 1 https://github.com/georgekhananaev/claude-skills-vault

Made for: Claude Code.

Wrote 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.

agentmods badge for upgrade-packages-js

README.md
[![agentmods](https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/upgrade-packages-js/github.svg)](https://agentmods.dev/skills/georgekhananaev/claude-skills-vault/upgrade-packages-js)
Your own site
<a href="https://agentmods.dev/skills/georgekhananaev/claude-skills-vault/upgrade-packages-js"><img src="https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/upgrade-packages-js/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.

agentmods 80×15 button for upgrade-packages-js

Your own site · 80×15
<a href="https://agentmods.dev/skills/georgekhananaev/claude-skills-vault/upgrade-packages-js"><img src="https://agentmods.dev/badge/skills/georgekhananaev/claude-skills-vault/upgrade-packages-js.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,628 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.05628
Opus 5 $0.00019 $0.02814
Sonnet 5 $0.00008 $0.01126
Haiku 4.5 $0.00004 $0.00563

Measured 9d ago against content hash d5cd5107a50c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade C, and why

upgrade-packages-js scanned grade C with 2 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 9d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

| Cache issues | `rm -rf .next node_modules/.cache` |

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

node -e "const {execSync}=require('child_process');const run=(c)=>execSync(c,{stdio:['ignore','pipe','pipe']}).toString().trim();try{run('git --version')}catch(e){console.error('ERROR: git not installed');process.exit(10
.claude/skills/upgrade-packages-js/SKILL.md · 624 lines

How it starts

The opening of the file, as written. The whole thing — 624 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Skill: Package Upgrade (Cross-Platform)

Safely upgrade JavaScript packages while minimizing breaking change risk, with migration guidance and automated code upgrades.


Non-Negotiables

  1. Verify JavaScript project first - Stop immediately if not a JS/Node.js project
  2. Never force upgrade all at once - Upgrade incrementally
  3. Detect package manager first - npm/pnpm/yarn (including version)
  4. Never mix package managers - Refuse if lockfiles conflict
  5. Git safety gate first - Clean repo + new branch before upgrades
  6. Breaking-change evidence check - For majors, check Releases/CHANGELOG/Migration/Codemods
  7. For breaking upgrades: migrate code + tests - Apply codemods, implement fixes, add tests
  8. Check peer dependencies - Ensure compatibility before upgrading
  9. Check Node.js engine compatibility - Verify target versions support project's Node
  10. Check ESM/CJS compatibility - Verify module system compatibility
  11. Test after each major upgrade - Run build and tests
  12. Keep lockfile updated - Commit lockfile changes
  13. Document skipped packages - Record why packages were not upgraded
  14. Time-box upgrades - Max time per major; if stuck, defer and document

Project Language Detection (MANDATORY - RUN FIRST)

This skill is for JavaScript/TypeScript (Node.js) projects only. Run this check before anything else.

node -e "
const fs=require('fs'),p=require('path'),cwd=process.cwd();
const checks=[
  ['package.json','javascript/typescript','This skill supports this project type'],
  ['go.mod','go','Use: go get -u ./... or go-mod-upgrade'],
  ['Cargo.toml','rust','Use: cargo update or cargo-upgrades'],
  ['requirements.txt','python','Use: pip-review --auto or pip-upgrader'],
  ['pyproject.toml','python','Use: poetry update or pdm update'],
  ['Pipfile','python','Use: pipenv update'],
  ['composer.json','php','Use: composer update'],
  ['Gemfile','ruby','Use: bundle update'],
  ['pubspec.yaml','dart','Use: dart pub upgrade'],
  ['pom.xml','java','Use: mvn versions:use-latest-releases'],
  ['build.gradle','java','Use: gradle dependencyUpdates'],
  ['*.csproj','dotnet','Use: dotnet outdated or nukeeper'],
  ['Package.swift','swift','Use: swift package update'],
  ['mix.exs','elixir','Use: mix deps.update --all'],
];
const found=checks.filter(([f])=>f.includes('*')?require('fs').readdirSync(cwd).some(x=>x.endsWith(f.slice(1))):fs.existsSync(p.join(cwd,f)));
if(found.length===0){console.error('ERROR: No recognized project files found');process.exit(1)}
const js=found.find(([_,l])=>l==='javascript/typescript');
if(js){console.log('OK: JavaScript/TypeScript project detected (package.json found)');process.exit(0)}
const other=found[0];
console.error('ERROR: This skill is for JavaScript/TypeScript (Node.js) projects only.');
console.error('Detected: '+other[0]+' ('+other[1]+' project)');
console.error('Suggestion: '+other[2]);
process.exit(2);
"

Read the full file on GitHub · 624 lines

Files

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.

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.

  1. 9d ago First seen · 624 lines · 38 tokens per session scan C d5cd5107a50c

Subscribe to this mod's changes

upgrade-packages-js is a skill published in the GitHub repository georgekhananaev/claude-skills-vault (28 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 5,628 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (recursive force delete, runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

nodejs-runtime

Use this skill when the user needs to install, upgrade, or troubleshoot Node.js, npm, pnpm, yarn, and JavaScript/TypeScript runtime environments. Covers four-tier fallback strategy: (1) DesireCore HTTP API for in-app installation, (2) DesireCore built-in Volta CLI for Node.js + package manager version management, (3)…

desirecore/market · 230 tokens

cargo-release

PM-invocable protocol for Cargo publish and release operations in the trusty-tools Rust monorepo: semver rules, 10-step release sequence, macOS codesign safety, and cross-crate dependency ordering.

bobmatnyc/claude-mpm-skills · 45 tokens

code-formatter-installer

Installs and configures Prettier, ESLint, EditorConfig, and other code quality tools to enforce consistent code style across the team. Generates config files, npm scripts, editor settings recommendations, and CI integration suggestions. Use when users request "setup prettier", "add eslint", "configure code…

patricio0312rev/skillset · 75 tokens

github-copilot-upgrader

Use this to update the Github Copilot CLI/SDK.

microsoft/vscode · 18 tokens

commit

Commit staged or unstaged changes with an AI-generated commit message that matches the repository's existing commit style. Use when the user asks to 'commit', 'commit changes', 'create a commit', 'save my work', or 'check in code'.

microsoft/vscode · 52 tokens

create-pr

Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.

prisma/orm · 48 tokens