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 pledgeandgrow/pledge-skills --skill npmgit clone --depth 1 https://github.com/pledgeandgrow/pledge-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/pledgeandgrow/pledge-skills/npm)<a href="https://agentmods.dev/skills/pledgeandgrow/pledge-skills/npm"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/npm/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/pledgeandgrow/pledge-skills/npm"><img src="https://agentmods.dev/badge/skills/pledgeandgrow/pledge-skills/npm.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.00091 | $0.00915 |
| Opus 5.5 | $0.00036 | $0.00366 |
| Sonnet 5.5 | $0.00018 | $0.00183 |
| Haiku 4.5 | $0.00009 | $0.00092 |
Grade A, and why
npm-docs 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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
npm Documentation
Quick Reference
| Topic | File | Description |
|---|---|---|
| About npm | about-npm.md |
npm overview, registry, packages, modules, scopes, public/private packages |
| Getting Started | getting-started.md |
User accounts, 2FA, profile, billing, local env setup, installing Node.js & npm |
| package.json | package-json.md |
package.json fields, dependencies, semver, README, Node.js modules |
| Publishing | publishing.md |
Creating & publishing unscoped/scoped/private/org packages, dist-tags |
| Managing Packages | managing-packages.md |
Updating, deprecating, transferring, unpublishing, visibility, collaborators |
| Installing Packages | installing-packages.md |
Searching, downloading locally/globally, updating, uninstalling, EACCES |
| Security | security.md |
Audit, provenance, OIDC, staged publishing, signatures, 2FA, malware |
| Integrations | integrations.md |
External services, access tokens, CI/CD, Docker |
| Organizations | organizations.md |
Creating/managing orgs, billing, members, teams, org packages |
| CLI Commands | cli-commands.md |
All npm CLI commands reference (v12) |
| Configuring npm | configuring-npm.md |
.npmrc, package.json, package-lock.json, folders, install |
| Using npm | using-npm.md |
Registry, package spec, config, logging, scope, scripts, workspaces |
| Troubleshooting | troubleshooting.md |
Common errors, debug logs, version issues |
| Policies | policies.md |
Terms, conduct, disputes, license, privacy, unpublish, DMCA, security |
Core Concepts
- npm — Node Package Manager; package registry, CLI, and website
- Package — A file/directory described by
package.json - Module — Any file/directory in
node_modulesloadable viarequire()orimport - Scope — A namespace for packages (e.g.,
@myorg/mypackage) - Semantic Versioning —
MAJOR.MINOR.PATCHversioning scheme - Registry — The public npm registry at
https://registry.npmjs.org - Organization — A group for coordinating package maintenance and collaboration
- Access Token — Authentication token for CLI/API access
- Workspaces — Monorepo support for managing multiple packages
What ships with it
14 files 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.
- about-npm.md 5.3 KB
- cli-commands.md 11 KB
- configuring-npm.md 5.9 KB
- getting-started.md 4.4 KB
- installing-packages.md 4.7 KB
- integrations.md 4.9 KB
- managing-packages.md 3.5 KB
- organizations.md 4.5 KB
- package-json.md 5.9 KB
- policies.md 7.3 KB
- publishing.md 3.5 KB
- security.md 5.3 KB
- troubleshooting.md 5.2 KB
- using-npm.md 13 KB
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.
- 1mo ago First seen · 101 lines · 91 tokens per session scan A af0a2ac9b87a
npm-docs is a skill published in the GitHub repository pledgeandgrow/pledge-skills (10 stars, last pushed 3mo ago), licensed MIT. It adds 91 tokens to every session and 915 once invoked, about $0.0004 per session on Opus 5.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
skillpm
Install, list, update, scaffold, publish, and sync npm-distributed Agent Skills with skillpm. Use when managing skill dependencies, packaging skills for npm, or refreshing agent directories after dependency or local skill changes.
dss-query
Explain and compose vlt Dependency Selector Syntax (DSS) queries — CSS-selector-like strings for filtering packages in a dependency graph, including Socket-powered security auditing. Use when the user asks about DSS, vlt query, dependency selectors, wants to find/filter packages (e.g. "find outdated deps", "select all…
github-packages-npm
Publish or consume scoped npm packages through GitHub Packages, configure registry authentication, and troubleshoot package access.
vlt-registry-migration
Moves a JavaScript repository (single package or monorepo) onto a vlt.io registry. Routes installs through the account's npm mirror and private main registry, handles the lockfile, and sets up auth for npm, pnpm, yarn, bun, deno and the vlt CLI on laptops, CI, Vercel and coding-agent sandboxes. Use when the user wants…
npm-search
Search npm packages, compare libraries, and check download stats via MCP. Use when evaluating or researching npm packages.
ship-safe-baseline
Manage your security baseline — accept current findings as known debt, then only report new regressions on future scans. Use when the user wants to adopt security scanning incrementally or suppress existing findings.