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/caiaffa/claude-code-ultimate-engineering-system/node-runtime-reliabilitynpx skills add caiaffa/claude-code-ultimate-engineering-system --skill node-runtime-reliabilitygit clone --depth 1 https://github.com/caiaffa/claude-code-ultimate-engineering-systemWhat 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.00030 | $0.00674 |
| Opus 5 | $0.00015 | $0.00337 |
| Sonnet 5 | $0.00006 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
node-runtime-reliability 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 2d 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 — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mission
Make Node.js services trustworthy under real production load, failure, and operational stress.
When to use
- Reviewing Node.js service reliability.
- Investigating latency, crashes, or memory issues.
- Designing async workflows.
- Validating shutdown, retries, and concurrency controls.
Handoff
- Receives from: backend-platform-engineer (implementation) or systematic-debugging (investigation).
- Hands off to: performance-analysis (if perf issue), otel-observability-architect (monitoring), kubernetes-operability (runtime config).
Node.js runtime risks
| Risk | Symptom | Detection | Fix |
|---|---|---|---|
| Event loop blocking | All requests slow simultaneously | Event loop lag metric > 100ms | Move CPU work to worker threads or separate process |
| Unhandled promise rejection | Silent failure, missing data | unhandledRejection handler + logging |
Always await or catch; add process handler as safety net |
| Memory leak | RSS grows over hours/days | RSS metric trending up over 24h | Heap snapshot analysis; check caches, listeners, closures |
| Unbounded concurrency | Dependency overwhelmed | Connection pool exhaustion, timeout spikes | Semaphore/queue limiting concurrent requests |
| Missing cancellation | Work continues after request abandoned | CPU/memory usage without matching traffic | AbortController for HTTP calls; cancel tokens for async chains |
| Bad shutdown | Jobs lost, connections leaked | Restart produces duplicate work or errors | SIGTERM handler: stop accepting, drain in-flight, close pools |
Shutdown implementation pattern
process.on('SIGTERM', async () => {
server.close(); // Stop accepting new connections
await drainInFlightRequests(); // Wait for current requests (with timeout)
await closeConnectionPools(); // DB, Redis, etc.
await flushTelemetry(); // Send remaining spans/metrics
process.exit(0);
});
Concurrency control pattern
// BAD: unbounded concurrent external calls
const results = await Promise.all(items.map(i => callExternalAPI(i)));
// GOOD: bounded concurrency
import pLimit from 'p-limit';
const limit = pLimit(10); // max 10 concurrent
const results = await Promise.all(items.map(i => limit(() => callExternalAPI(i))));
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.
- 2d ago First seen · 66 lines · 30 tokens per session scan A 7b72d99d1539
node-runtime-reliability is a skill published in the GitHub repository caiaffa/claude-code-ultimate-engineering-system (16 stars, last pushed 2mo ago), licensed MIT. It adds 30 tokens to every session and 674 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…