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/jesus-seijas-sp/claude-node-setup/nodejsnpx skills add jesus-seijas-sp/claude-node-setup --skill nodejsgit clone --depth 1 https://github.com/jesus-seijas-sp/claude-node-setupWrote 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/jesus-seijas-sp/claude-node-setup/nodejs)<a href="https://agentmods.dev/skills/jesus-seijas-sp/claude-node-setup/nodejs"><img src="https://agentmods.dev/badge/skills/jesus-seijas-sp/claude-node-setup/nodejs.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.00019 | $0.00398 |
| Opus 5 | $0.00010 | $0.00199 |
| Sonnet 5 | $0.00004 | $0.00080 |
| Haiku 4.5 | $0.00002 | $0.00040 |
Grade A, and why
nodejs 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
Node.js Skill
Use this skill when writing any Node.js JavaScript code: modules, async logic, error handling, project structure, or environment configuration.
When to Use
- Writing or reviewing any Node.js source file
- Working with ESM modules, imports, and exports
- Handling async operations, Promises, or streams
- Managing environment variables and configuration
- Structuring a Node.js project
- Documenting API endpoints with Swagger/OpenAPI
Rules
- rules/esm.md — ESM module system: imports, exports, file extensions, dynamic imports.
- rules/async.md — Async/await, Promise patterns, error propagation, concurrency.
- rules/error-handling.md — Error types, propagation, process-level handlers, safe coding.
- rules/project-structure.md — Feature-oriented directory layout, config, environment variables, entry points.
- rules/swagger.md — JSDoc @swagger blocks with swagger-jsdoc: schemas, routes, parameters, tags.
Quick Reference
// ESM import — always use .js extension for local files
import { createUser } from './users.js';
import { readFile } from 'node:fs/promises';
// Async function — always propagate errors, never swallow
async function loadConfig(path) {
const raw = await readFile(path, 'utf8');
return JSON.parse(raw);
}
// Concurrent work — use Promise.all, not sequential awaits
const [users, products] = await Promise.all([getUsers(), getProducts()]);
What ships with it
5 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.
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 · 49 lines · 19 tokens per session scan A 2e29fb5e3c58
nodejs is a skill published in the GitHub repository jesus-seijas-sp/claude-node-setup (10 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 398 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-31.
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…