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 spencerpauly/awesome-cursor-skills --skill updating-npm-packagegit clone --depth 1 https://github.com/spencerpauly/awesome-cursor-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/spencerpauly/awesome-cursor-skills/updating-npm-package)<a href="https://agentmods.dev/skills/spencerpauly/awesome-cursor-skills/updating-npm-package"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/updating-npm-package/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/spencerpauly/awesome-cursor-skills/updating-npm-package"><img src="https://agentmods.dev/badge/skills/spencerpauly/awesome-cursor-skills/updating-npm-package.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 83 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 112 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00062 | $0.00931 |
| Opus 5 | $0.00031 | $0.00465 |
| Sonnet 5 | $0.00012 | $0.00186 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
updating-npm-package 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 13d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Updating an npm Package
Use this skill when the user asks to update, upgrade, or bump a specific npm dependency.
Steps
-
Check the current version — read
package.jsonto find the installed version:npm ls <package-name> -
Find the latest version on npm — fetch the package info:
npm view <package-name> versions --json npm view <package-name> dist-tags --jsonThis gives you the
latesttag and all published versions. -
Determine the update type — compare current version to latest:
- Patch (1.2.3 → 1.2.4): bug fixes only
- Minor (1.2.3 → 1.3.0): new features, backwards compatible
- Major (1.2.3 → 2.0.0): breaking changes
-
For patch or minor updates — just do it:
npm install <package-name>@latestRun the build and tests to make sure nothing broke:
npm run build && npm testIf everything passes, commit and report what changed.
-
For major updates — do a thorough investigation first:
a. Fetch the changelog and release notes — check the package's GitHub repo for
CHANGELOG.md,MIGRATION.md, or release notes. Use the web to find the official upgrade guide:Search: "<package-name> v<major> migration guide" OR "<package-name> v<major> upgrade guide"b. Read the breaking changes — identify every breaking change between the current and target version. Common things to check:
- Removed or renamed APIs
- Changed function signatures or return types
- Dropped Node.js version support
- New peer dependency requirements
- Changed default behavior
- Config file format changes
c. Scan the codebase for impact — search for every usage of the package:
# Find all imports grep -r "from ['\"]<package-name>" src/ grep -r "require(['\"]<package-name>" src/For each usage, check if it's affected by a breaking change.
d. Apply the update:
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.
- 13d ago First seen · 114 lines · 62 tokens per session scan A 0e353496268d
updating-npm-package is a skill published in the GitHub repository spencerpauly/awesome-cursor-skills (772 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 62 tokens to every session and 931 once invoked, about $0.0003 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
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…