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/shahtuyakov/claude-setup/node-backendnpx skills add shahtuyakov/claude-setup --skill node-backendgit clone --depth 1 https://github.com/shahtuyakov/claude-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/shahtuyakov/claude-setup/node-backend)<a href="https://agentmods.dev/skills/shahtuyakov/claude-setup/node-backend"><img src="https://agentmods.dev/badge/skills/shahtuyakov/claude-setup/node-backend.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.00055 | $0.00687 |
| Opus 5 | $0.00028 | $0.00344 |
| Sonnet 5 | $0.00011 | $0.00137 |
| Haiku 4.5 | $0.00006 | $0.00069 |
Grade A, and why
node-backend 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.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js Backend
Patterns and best practices for Node.js backend development with TypeScript.
Framework Selection
| Framework | Best For | Use When |
|---|---|---|
| Express | Simple APIs, flexibility | Quick setup, full control needed |
| NestJS | Enterprise, structured | Large teams, Angular-like structure |
| Fastify | Performance critical | High throughput, schema validation |
| Hono | Edge, lightweight | Cloudflare Workers, minimal overhead |
Reference Files
| Topic | Load | Use When |
|---|---|---|
| Project structure | references/project-structure.md |
Setting up new project or organizing code |
| Express patterns | references/express-patterns.md |
Building with Express |
| NestJS patterns | references/nestjs-patterns.md |
Building with NestJS |
| Auth implementation | references/auth-patterns.md |
Implementing authentication |
| Error handling | references/error-handling.md |
Setting up error handling |
| Validation | references/validation.md |
Input validation patterns |
Quick Start Patterns
Express Basic Setup
import express from 'express';
import cors from 'cors';
import helmet from 'helmet';
import { errorHandler } from './middleware/errorHandler';
import { routes } from './routes';
const app = express();
app.use(helmet());
app.use(cors());
app.use(express.json());
app.use('/api', routes);
app.use(errorHandler);
export { app };
NestJS Module Pattern
@Module({
imports: [TypeOrmModule.forFeature([User])],
controllers: [UsersController],
providers: [UsersService],
exports: [UsersService],
})
export class UsersModule {}
TypeScript Configuration
{
"compilerOptions": {
"target": "ES2022",
"module": "NodeNext",
"moduleResolution": "NodeNext",
"strict": true,
"esModuleInterop": true,
"skipLibCheck": true,
"outDir": "./dist",
"rootDir": "./src",
"declaration": true
}
}
Essential Packages
What ships with it
6 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 · 104 lines · 55 tokens per session scan A ee98b6e18d1d
node-backend is a skill published in the GitHub repository shahtuyakov/claude-setup (13 stars, last pushed 8mo ago), licensed MIT. It adds 55 tokens to every session and 687 once invoked, about $0.0003 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
typescript-best-practices
TypeScript/Node.js best practices. Use when writing or reviewing TypeScript code. Covers type safety, async patterns, and error handling.
node
Provides domain-specific best practices for Node.js development with TypeScript, covering type stripping, async patterns, error handling, streams, modules, testing, performance, caching, logging, and more. Use when setting up Node.js projects with native TypeScript support, configuring type stripping…
fastify-best-practices
Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication…
typescript-magician
Designs complex generic types, refactors any types to strict alternatives, creates type guards and utility types, and resolves TypeScript compiler errors. Use when the user asks about TypeScript (TS) types, generics, type inference, type guards, removing any types, strict typing, type errors, infer, extends…
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.
skill-context-detection
Auto-detect work context (Dev vs Knowledge) — use to tailor workflows based on current task type.