Borrowing it
Nothing to install: this file belongs to thunder-id/thunderid. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thunder-id/thunderid/main/.agent/skills/prune-npm-overrides/SKILL.mdgit clone --depth 1 https://github.com/thunder-id/thunderidWrote 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/thunder-id/thunderid/prune-npm-overrides)<a href="https://agentmods.dev/skills/thunder-id/thunderid/prune-npm-overrides"><img src="https://agentmods.dev/badge/skills/thunder-id/thunderid/prune-npm-overrides/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/thunder-id/thunderid/prune-npm-overrides"><img src="https://agentmods.dev/badge/skills/thunder-id/thunderid/prune-npm-overrides.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00071 | $0.02097 |
| Opus 5 | $0.00036 | $0.01048 |
| Sonnet 5 | $0.00014 | $0.00419 |
| Haiku 4.5 | $0.00007 | $0.00210 |
Grade A, and why
prune-npm-overrides 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 6d 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prune npm Overrides
fix-npm-vulnerability adds an override when no upstream fix exists yet. This skill is the other half: it goes back through the overrides already in the tree and retires the ones that are no longer doing anything.
An override is a workaround, not a fix. It pins a transitive package past what a head dependency asks for, and it keeps doing that long after the head dependency ships a release with a patched range. Left unaudited, overrides: only grows, and every stale entry constrains unrelated upgrades.
Each entry ends the run in exactly one of three states:
| Outcome | Condition | Action |
|---|---|---|
| Remove | Tree already resolves to a patched version without the pin, or pnpm why reports nothing at all |
Delete the entry, close its tracking issue |
| Replace | The package is a direct workspace dependency | Bump it (or its catalog entry) and delete the override |
| Keep | Still resolves to an affected version and no head dependency release fixes it | Keep the entry, ensure it carries a full justification comment |
Step 1 - Locate the workspace root
dir=$(pwd); while [ "$dir" != "/" ]; do [ -f "$dir/pnpm-workspace.yaml" ] && echo "$dir" && break; dir=$(dirname "$dir"); done
All subsequent commands run from this root.
Step 2 - Inventory every override declaration
Overrides hide in more places than the root file:
# Root workspace overrides (the ones pnpm actually honors)
grep -n -A200 '^overrides:' pnpm-workspace.yaml
# Per-package blocks: ignored by pnpm at install time, but honored by npm
grep -rn --include=package.json -E '"(overrides|resolutions)"' . | grep -v node_modules
A per-package overrides block in a workspace member is either dead weight or a sign that the package is also installed standalone with npm (samples are the usual case). Determine which before touching it, and do not delete one just because pnpm ignores it.
Build a table before changing anything, one row per entry:
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.
- 6d ago First seen · 190 lines · 71 tokens per session scan A 9456ed0f3c79
prune-npm-overrides is a skill published in the GitHub repository thunder-id/thunderid (574 stars, last pushed today), licensed Apache-2.0. It adds 71 tokens to every session and 2,097 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
jwt
Development guide for the jwt JSON Web Token library for Go (github.com/kataras/jwt). Use this skill when signing or verifying JWTs, choosing a signing algorithm (HMAC, RSA, RSA-PSS, ECDSA, EdDSA), reading or validating standard or custom claims, setting expiry and clock-skew tolerance, rotating keys with a kid-based…
conventional-commit
Workflow for generating conventional commit messages following the Conventional Commits specification. MUST be invoked every time a commit is created. Guides construction of standardized commit messages with correct type, scope, description, body, and footer.
markdown
Markdown formatting rules for this project. Apply when writing or editing any .md or .mdx file, including documentation and website content.
oh-my-posh
Install, configure, or troubleshoot Oh My Posh/ohmyposh: shell init, themes, segments, Nerd Font icons, and prompt setup on PowerShell, zsh, bash, or fish.
migrate-goldmark-extension-v1-to-v2
Migrate goldmark extension from goldmark v1 to v2.
use-modern-go
Use the Modern Go Guidelines CLI whenever writing, modifying, fixing, or refactoring Go code. Apply its version-specific guidance to generated changes.