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 FutureJJ/claude-skills --skill nodejs-backendgit clone --depth 1 https://github.com/FutureJJ/claude-skillsWrote 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/futurejj/claude-skills/nodejs-backend)<a href="https://agentmods.dev/skills/futurejj/claude-skills/nodejs-backend"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/nodejs-backend/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/futurejj/claude-skills/nodejs-backend"><img src="https://agentmods.dev/badge/skills/futurejj/claude-skills/nodejs-backend.svg" alt="Reviewed on agentmods" width="80" 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.00059 | $0.00320 |
| Opus 5.5 | $0.00024 | $0.00128 |
| Sonnet 5.5 | $0.00012 | $0.00064 |
| Haiku 4.5 | $0.00006 | $0.00032 |
Grade A, and why
nodejs-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 1mo 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 Backend
You are a Node.js backend expert focused on production-grade APIs and performance.
Core Principles
- Fastify over Express for new projects. Fastify is faster, has built-in schema validation, and better TypeScript support.
- Streams for large data. Never load entire files into memory. Pipe streams.
- Proper error handling. Unhandled rejections crash the process. Use error middleware and process-level handlers.
- Structured logging. Use pino (not console.log). Include request IDs, timestamps, context.
Anti-Patterns
- Callback hell — use async/await
- Blocking the event loop with CPU-intensive work — use worker threads
- Not handling process signals (SIGTERM/SIGINT) — connections hang on deploy
- Using
*CORS in production — be explicit about allowed origins
Reference Guide
| Topic | Reference | Load When |
|---|---|---|
| Express/Fastify patterns | references/frameworks.md |
Routing, middleware, validation |
| Streams & performance | references/streams.md |
File handling, backpressure, workers |
| Error handling | references/error-handling.md |
Error middleware, graceful shutdown |
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.
- 1mo ago First seen · 31 lines · 59 tokens per session scan A 658f8712de54
nodejs-backend is a skill published in the GitHub repository FutureJJ/claude-skills (3 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 320 once invoked, about $0.0002 per session on Opus 5.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
auth-architect
Designs and implements authentication and identity systems. Covers OAuth2 and OIDC flows including authorization code, PKCE, and client credentials; JWT design including RS256 vs HS256, key rotation, token blacklisting, and refresh token strategy; RBAC and ABAC modeling; SSO with Google, GitHub, and SAML 2.0; session…
api-sculptor
Designs and implements APIs: REST, GraphQL, gRPC, and WebSocket. Produces OpenAPI 3.1 specs, GraphQL SDL schemas, Protocol Buffer definitions, and working server implementations. Use this skill when the user asks about API design, endpoint structure, schema definition, versioning strategy, pagination, authentication…
swift-networking
Builds a protocol-based async/await networking layer with URLSession, testable abstractions, error handling, and mock support for Swift projects. Use when user says "add networking", "create an API layer", "fetch data from API", "build a network service", "add URLSession", "implement HTTP requests", "create a REST…
offensive-api-abuse
Advanced API exploitation methodology focused on business logic abuse and sophisticated attack patterns that bypass traditional security controls. Covers business logic bypass through API call chaining and workflow manipulation. Addresses GraphQL-specific attacks including batching for credential brute-force, query…
offensive-graphql
Offensive methodology for attacking GraphQL APIs during penetration tests and bug bounty engagements. Covers the full attack lifecycle: endpoint discovery, introspection abuse and blind schema reconstruction when introspection is disabled, authentication and authorization bypass through Relay node IDs and nested…
telegram
Send Telegram messages, files, and alerts via bot API; read replies; ask questions with inline buttons and wait for the answer (approve-from-phone). Supports multiple bots and named chat targets. Use when the user wants to send a Telegram message or alert, get notified on Telegram when a task finishes or needs input…