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 NitorCreations/nitor-agent-skills --skill npm-supply-chain-auditgit clone --depth 1 https://github.com/NitorCreations/nitor-agent-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/nitorcreations/nitor-agent-skills/npm-supply-chain-audit)<a href="https://agentmods.dev/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit"><img src="https://agentmods.dev/badge/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit/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/nitorcreations/nitor-agent-skills/npm-supply-chain-audit"><img src="https://agentmods.dev/badge/skills/nitorcreations/nitor-agent-skills/npm-supply-chain-audit.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00099 | $0.03550 |
| Opus 5 | $0.00049 | $0.01775 |
| Sonnet 5 | $0.00020 | $0.00710 |
| Haiku 4.5 | $0.00010 | $0.00355 |
Grade A, and why
npm-supply-chain-audit 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 12d 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 — 282 lines — stays where its author put it; the contents beside it link to each section on GitHub.
npm supply-chain security audit
Audit the current repo for npm supply-chain security issues, present findings to the user, and apply fixes only after confirmation.
Step 1 – Detect the package manager
Check which package manager(s) are in use:
package-lock.json-> npmaube-lock.yaml-> Aubepnpm-lock.yaml-> pnpmyarn.lock+.yarnrc.yml-> Yarn Berry;yarn.lockwithout.yarnrc.yml-> Yarn Classicbun.lockborbun.lock-> BunpackageManagerfield inpackage.jsonconfirms the PM and version
Use the packageManager field to determine the version. If not present, run the PM's --version command. The version is needed for checks that depend on minimum PM versions (e.g. pnpm 10+, pnpm 11+, npm 11.10+, npm 12+, Yarn Berry 4.10+, Bun 1.3+).
pnpm 11 ships several supply-chain protections on by default (minimumReleaseAge: 1440, blockExoticSubdeps: true, strictDepBuilds: true) and only reads pnpm-specific settings from pnpm-workspace.yaml (or ~/.config/pnpm/config.yaml), not from .npmrc. Many checks below differ between pnpm 10 and pnpm 11+.
npm 12 (estimated July 2026) similarly ships protections on by default: dependency lifecycle scripts are blocked unless approved via the allowScripts field in package.json, and git and remote-URL dependencies are blocked (allow-git and allow-remote default to none). Several checks below differ between npm 11 and npm 12+.
If no lockfile exists, default to npm.
Step 2 – Audit
Work through the checks below. For each one, check the current state and record whether it passes or needs a fix. Do NOT make any changes yet.
2.1 Lockfile committed
If no lockfile exists (package-lock.json, pnpm-lock.yaml, yarn.lock, bun.lockb, bun.lock, aube-lock.yaml), warn the user they should run their package manager's install command and commit the lockfile. Do NOT run install yourself.
2.2 Block lifecycle scripts
npm 12+ – blocks dependency lifecycle scripts (preinstall, install, postinstall, and prepare for git/file/link dependencies) by default; only packages approved in the allowScripts field of package.json may run them. Check that .npmrc does not loosen this with a broad allow-scripts setting, and review existing allowScripts entries – flag any untrusted packages approved there.
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.
- 12d ago First seen · 282 lines · 99 tokens per session scan A b222954a1708
npm-supply-chain-audit is a skill published in the GitHub repository NitorCreations/nitor-agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 3,550 once invoked, about $0.0005 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-31.
Other skills, from other repositories
no-bare-casts
Writing as in TypeScript or TSX production code, modifying a file that contains a bare as cast, silencing a type error with a cast, encountering as unknown as, or reviewing a cast site.
aws-sst-development
SST v4 (Ion) expert for managing AWS resources as code with the Pulumi-backed framework.
league-akari-shard-development
Use when creating, extending, refactoring, splitting, or reviewing League Akari main or renderer shards, including shard file organization, controller/loader/executor/handler boundaries, naming conventions, renderer TSX usage, platform guards, and public contract compatibility.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
fast-typescript-check
Keep www-sacred's TypeScript fast to type-check and fast to run. Use when touching the ASCII/canvas animation components (the only real per-frame code here), tightening type-check wall-clock, or auditing a change for runtime or compiler regressions. Scoped to this repo — a React 19 / Next.js 16 component library plus…
migrate-better-result-3
Migrate a TypeScript codebase from better-result 2.x to 3.0. Use when upgrading better-result across the TaggedError syntax, removed Result serialization helpers, recovery inference, matching, or retry APIs.