migrate-to-pnpm-11

migrate-to-pnpm-11 is a skill for Claude Code from llbbl/pnpm-upgrade-skills. It costs 107 tokens per session (7,059 once invoked), scanned D, original, MIT.

A migration guide moves a JavaScript or TypeScript project from npm, Yarn, or an older pnpm version to pnpm 11. pnpm is a tool that installs and manages project packages.

In plain words
What is it for?
Use it when upgrading to pnpm 11, switching package managers, or adding its supply-chain safeguards to an existing project.
Why use it?
It helps update the package-management setup while applying pnpm 11 checks for package age, dependency sources, build scripts, lockfiles, and package signatures.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it when upgrading to pnpm 11, switching package managers, or adding its supply-chain safeguards to an existing project.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/llbbl/pnpm-upgrade-skills/migrate-to-pnpm-11
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 llbbl/pnpm-upgrade-skills --skill migrate-to-pnpm-11
Clone the repo
git clone --depth 1 https://github.com/llbbl/pnpm-upgrade-skills

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 migrate-to-pnpm-11

README.md
[![agentmods](https://agentmods.dev/badge/skills/llbbl/pnpm-upgrade-skills/migrate-to-pnpm-11/github.svg)](https://agentmods.dev/skills/llbbl/pnpm-upgrade-skills/migrate-to-pnpm-11)
Your own site
<a href="https://agentmods.dev/skills/llbbl/pnpm-upgrade-skills/migrate-to-pnpm-11"><img src="https://agentmods.dev/badge/skills/llbbl/pnpm-upgrade-skills/migrate-to-pnpm-11/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 migrate-to-pnpm-11

Your own site · 80×15
<a href="https://agentmods.dev/skills/llbbl/pnpm-upgrade-skills/migrate-to-pnpm-11"><img src="https://agentmods.dev/badge/skills/llbbl/pnpm-upgrade-skills/migrate-to-pnpm-11.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 107 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,059 The whole file, excluding the scripts and references it only reads on demand.
Security scan D 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.00107 $0.07059
Opus 5.5 $0.00043 $0.02824
Sonnet 5.5 $0.00021 $0.01412
Haiku 4.5 $0.00011 $0.00706

Measured 2mo ago against content hash 72683ac497ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade D, and why

migrate-to-pnpm-11 scanned grade D 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 2mo 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.

Asks for rootmediumPrivilege escalation

A mod that escalates privileges can change anything on the machine, not only the project.

sudo corepack enable

Recursive force deletehighDestructive command

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

rm -rf node_modules
claude/migrate-to-pnpm-11/SKILL.md · 734 lines

How it starts

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

/migrate-to-pnpm-11

Migrate a project to pnpm 11 and adopt its supply-chain security defaults.

Why pnpm 11

pnpm 11 (released 2026-04-28) turns on five supply-chain defaults that were opt-in or absent before:

Setting Default in v11 Purpose
minimumReleaseAge 1440 (24 h) Refuse to install package versions younger than the cooldown window. Blocks the typical "publish-malware → wait for CI to pull it" window.
blockExoticSubdeps true Transitive deps cannot come from git URLs or arbitrary tarballs.
strictDepBuilds true Any dependency with a postinstall/build script that is not on the allowBuilds allowlist fails the install with ERR_PNPM_IGNORED_BUILDS.
verifyDepsBeforeRun install pnpm run <script> re-checks the lockfile before running.
optimisticRepeatInstall true Skip work when the lockfile is unchanged.

Plus: lockfile entries are re-validated against minimumReleaseAge even if the lockfile was committed under a weaker policy, Git-hosted deps get integrity pinning, and pnpm audit signatures verifies ECDSA registry signatures.

Prerequisites

  • Node.js ≥ 22. pnpm 11 is pure ESM and drops Node 18/20.
  • A clean working tree (or be willing to commit/stash before migrating — the migration touches lockfiles, package.json, .npmrc, and may create pnpm-workspace.yaml).

Git workflow

This skill does not run git commit, git push, or gh pr directly. After the migration is verified, summarize the changes for the user and let them (or a separate commit/PR workflow) handle the commit.

Before editing any files, create a feature branch. The migration touches lockfiles, package.json, .npmrc, pnpm-workspace.yaml, the Dockerfile, and CI configs — too much for a stray commit on main.

git status                       # confirm clean tree
git checkout -b chore/migrate-to-pnpm-11

If the working tree isn't clean, stop and ask the user how to proceed (stash, commit elsewhere, or abort). Do not migrate on top of unrelated in-progress work.

Read the full file on GitHub · 734 lines

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. 2mo ago First seen · 734 lines · 107 tokens per session scan D 72683ac497ae

Subscribe to this mod's changes

migrate-to-pnpm-11 is a skill published in the GitHub repository llbbl/pnpm-upgrade-skills (1 stars, last pushed 6mo ago), licensed MIT. It adds 107 tokens to every session and 7,059 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it D with 2 findings (asks for root, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

migrate-to-pnpm-11 compared with skills from other repositories

migrate-to-pnpm-11 next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
migrate-to-pnpm-11llbbl/pnpm-upgrade-skillsSkill16mo agoMITD107Claude Code
npm-securitybodadotsh/npm-security-best-practicesSkill8585d agoMITA43Claude Code, Codex
frontmcp-extensibilityagentfront/frontmcpSkill1535d agoApache-2.0A124Claude Code, Codex
javascript-expertpersonamanagmentlayer/pclSkill4525d agoApache-2.0A69Claude Code
ai-commit-msgstephansama/packagesSkill53d agoMITA182Claude Code, Codex
typed-eventsstephansama/packagesSkill53d agoMITA80Claude Code, Codex
astro-iconify-svgmapstephansama/packagesSkill53d agoMITA110Claude Code, Codex