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 agentmods add skills/espennilsen/pi/npmnpx skills add espennilsen/pi --skill npmgit clone --depth 1 https://github.com/espennilsen/piWrote 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/espennilsen/pi/npm)<a href="https://agentmods.dev/skills/espennilsen/pi/npm"><img src="https://agentmods.dev/badge/skills/espennilsen/pi/npm.svg" alt="Measured on agentmods" 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 | $0.00023 | $0.00391 |
| Opus 5 | $0.00012 | $0.00196 |
| Sonnet 5 | $0.00005 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
npm 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 4d 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.
What it actually says
NPM Skill
Use the npm tool to manage Node.js packages and run npm workflows.
Common workflows
Install dependencies
npm tool: action=install
npm tool: action=install, args="express @types/express --save-dev"
Run scripts
npm tool: action=run, args="dev"
npm tool: action=test
npm tool: action=build
Publish a package
Always do a dry run first to verify what will be published:
npm tool: action=publish, dry_run=true
Then publish for real:
npm tool: action=publish
npm tool: action=publish, args="--tag beta"
Version bumps
Preview first, then apply:
npm tool: action=version, args="patch", dry_run=true
npm tool: action=version, args="minor"
Check for issues
npm tool: action=outdated
npm tool: action=audit
npm tool: action=audit, args="--fix"
Inspect packages
npm tool: action=info, args="react"
npm tool: action=list, args="--depth=0"
Guidelines
- Before publishing, always read
package.jsonto verify name, version, files, and registry config. - Use
dry_run: truefor publish, pack, and version to preview before committing. - Check
npm outdatedbefore updating to understand what will change. - Run
npm auditafter installing new dependencies. - When working in a monorepo, use the
pathparameter to target specific packages.
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.
- 4d ago First seen · 63 lines · 23 tokens per session scan A e395db495ef3
npm is a skill published in the GitHub repository espennilsen/pi (117 stars, last pushed 11d ago), licensed MIT. It adds 23 tokens to every session and 391 once invoked, about $0.0001 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…