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 jesus-seijas-sp/claude-node-setup --skill documentationgit 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/documentation)<a href="https://agentmods.dev/skills/jesus-seijas-sp/claude-node-setup/documentation"><img src="https://agentmods.dev/badge/skills/jesus-seijas-sp/claude-node-setup/documentation.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.1 | $0.00021 | $0.00388 |
| Opus 5 | $0.00010 | $0.00194 |
| Sonnet 5 | $0.00004 | $0.00078 |
| Haiku 4.5 | $0.00002 | $0.00039 |
Grade A, and why
documentation 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.
What it actually says
Documentation Skill
Use this skill when asked to document code, generate architecture diagrams, explain how a module or feature works, or produce any form of technical reference material.
When to Use
- Documenting a function, class, or module
- Generating an architecture or component overview
- Describing a feature's data flow or business logic
- Creating or updating a README
- Producing inline JSDoc/TSDoc comments
Output Formats
- Prose: Always Markdown (
.md) - Diagrams: Always Mermaid (fenced
```mermaidblocks)
Rules
This skill is governed by the following rule documents:
- rules/markdown-conventions.md — Markdown structure, heading hierarchy, tables, code blocks, and callouts.
- rules/mermaid-diagrams.md — When and how to use each Mermaid diagram type, quality checklist, and examples.
- rules/documentation-workflow.md — Step-by-step process: read code → choose scope → write docs → output.
Quick Reference
| Scope | Primary structure | Diagram type |
|---|---|---|
| Function / method | API table (params, returns, example) | None unless complex |
| Module / file | Purpose + exports + internal structure | graph LR or classDiagram |
| Feature / flow | Overview + flow + key components | sequenceDiagram or flowchart TD |
| Full project | Architecture overview + module map | graph LR |
What ships with it
3 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.
- 6d ago First seen · 45 lines · 21 tokens per session scan A 8dadbf371098
documentation is a skill published in the GitHub repository jesus-seijas-sp/claude-node-setup (10 stars, last pushed 6mo ago), licensed MIT. It adds 21 tokens to every session and 388 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…