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 Miaoge-Ge/coding-agent-skills --skill nodejs-backend-expertgit clone --depth 1 https://github.com/Miaoge-Ge/coding-agent-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/miaoge-ge/coding-agent-skills/nodejs-backend-expert)<a href="https://agentmods.dev/skills/miaoge-ge/coding-agent-skills/nodejs-backend-expert"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/nodejs-backend-expert/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/miaoge-ge/coding-agent-skills/nodejs-backend-expert"><img src="https://agentmods.dev/badge/skills/miaoge-ge/coding-agent-skills/nodejs-backend-expert.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.00093 | $0.01181 |
| Opus 5.5 | $0.00037 | $0.00472 |
| Sonnet 5.5 | $0.00019 | $0.00236 |
| Haiku 4.5 | $0.00009 | $0.00118 |
Grade A, and why
nodejs-backend-expert 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.
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.
Node.js Backend Expert
The boundary is hostile: validate input, handle every rejection, and never trust the client. Keep handlers thin, push logic into services, and make the process production-safe (timeouts, health, graceful shutdown).
When to Use
- Building/structuring an HTTP API or service in Node (Express, Fastify, Hono…).
- Routing, middleware, input validation, auth, sessions, rate limiting.
- Unhandled-rejection, error-propagation, streaming, or backpressure issues.
- Project layout: transport → service → data layer.
When NOT to Use
- Next.js server features (RSC, server actions) →
nextjs-expert. - SQL/schema/indexing →
sql-expert. API contract design →api-design-expert. - Deep auth threat modeling/OWASP →
security-expert.
Core Principles
1. Layering
- Handlers/controllers stay thin (parse → call service → format response). Business logic lives in services; data access is isolated and mockable.
- Load config from env, validated at startup (
zod/envalid); fail fast on missing/invalid config. Noprocess.env.Xscattered through code.
2. Async & error discipline
async/awaitthroughout. Every route's thrown error must reach a central error handler — wrap async handlers (or use Fastify/Express 5 which await handlers natively).- Attach
process.on("unhandledRejection")/"uncaughtException"to log and exit; don't swallow. - Validate request body/query/params at the edge with a schema; reject early with 400 and a structured error.
3. Security baseline
helmetfor headers, explicit CORS allowlist, rate limiting on public/auth routes.- Hash passwords with
argon2/bcrypt; sign tokens/sessions with env secrets; cookiesHttpOnly+Secure+SameSite. Never log secrets, tokens, or full request bodies with PII. - Parameterize all DB access (no string-built SQL); cap body size.
4. Production-ready process
/health(liveness) + readiness; graceful shutdown onSIGTERM(stop accepting, drain in-flight, close DB pool).- Set server/socket timeouts. Stream large responses/uploads instead of buffering. Structured logging (
pino) with request IDs.
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 · 96 lines · 93 tokens per session scan A 8bfd6672e904
nodejs-backend-expert is a skill published in the GitHub repository Miaoge-Ge/coding-agent-skills (7 stars, last pushed 4mo ago), licensed MIT. It adds 93 tokens to every session and 1,181 once invoked, about $0.0004 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
springboot-patterns
Spring Boot architecture patterns, REST API design, layered services, data access, caching, async processing, and logging. Use for Java Spring Boot backend work.
django-patterns
Django architecture patterns, REST API design with DRF, ORM best practices, caching, signals, middleware, and production-grade Django apps.
api-design
REST API design patterns including resource naming, status codes, pagination, filtering, error responses, versioning, and rate limiting for production APIs.
backend-patterns
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
workflow-orchestration-patterns
Design durable workflows with Temporal for distributed systems. Covers workflow vs activity separation, saga patterns, state management, and determinism constraints. Use when building long-running processes, distributed transactions, or microservice orchestration.