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 instructions/jesus-seijas-sp/claude-node-setup/agents-mdgit 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/instructions/jesus-seijas-sp/claude-node-setup/agents-md)<a href="https://agentmods.dev/instructions/jesus-seijas-sp/claude-node-setup/agents-md"><img src="https://agentmods.dev/badge/instructions/jesus-seijas-sp/claude-node-setup/agents-md.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.00861 | $0.00861 |
| Opus 5 | $0.00430 | $0.00430 |
| Sonnet 5 | $0.00172 | $0.00172 |
| Haiku 4.5 | $0.00086 | $0.00086 |
Grade A, and why
claude-node-setup AGENTS.md 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 5d 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code — Project Instructions
This file provides guidance to AI coding agents (focuses in Claude Code) working in this repository.
What this repository is
A skills library for AI-assisted Node.js/JavaScript development with Fastify. Skills are Markdown documents that instruct AI agents how to write correct, idiomatic code for this stack.
Skills live under .claude/skills/<skill-name>/ and are the primary content of this repo.
Stack
| Concern | Technology |
|---|---|
| Runtime | Node.js (ESM, "type": "module") |
| Language | JavaScript |
| Web framework | Fastify |
| Logger | Pino (via fastify.log) |
| API docs | swagger-jsdoc + @fastify/swagger |
| Test runner | node --test (built-in) |
| Linter | ESLint |
| Formatter | Prettier |
Skills
Each skill is a self-contained guide. Read the relevant skill before writing code in that area.
| Skill | Path | Purpose |
|---|---|---|
fastify |
.claude/skills/fastify/SKILL.md |
Correct Fastify patterns: plugins, routes, schemas, lifecycle hooks |
nodejs |
.claude/skills/nodejs/SKILL.md |
Idiomatic Node.js/JavaScript: ESM, async, error handling, project structure, Swagger |
pino |
.claude/skills/pino/SKILL.md |
Logging with Pino: levels, context, child loggers, structured logs |
documentation |
.claude/skills/documentation/SKILL.md |
Producing Markdown docs and Mermaid diagrams |
security |
.claude/skills/security/SKILL.md |
Secure coding: input validation, injection prevention, auth, safe error handling, HTTP headers |
Common commands
Run from the repository root.
npm install # Install dependencies
npm run lintfix # ESLint --fix + Prettier
npm test # Run all tests (node --test)
Run a single test file:
node --test test/features/users/users.router.test.js
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.
- 5d ago First seen · 96 lines · 861 tokens per session scan A 9378c7879873
claude-node-setup AGENTS.md is an instructions file published in the GitHub repository jesus-seijas-sp/claude-node-setup (10 stars, last pushed 5mo ago), licensed MIT. It adds 861 tokens to every session, about $0.0043 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).