nodejs-expert

A Node.js and TypeScript development assistant. Node.js runs JavaScript outside a web browser, while TypeScript adds type checking to JavaScript.

In plain words
What is it for?
Use it for backend code, asynchronous programs, streams, performance work, npm packages, database libraries, validation, logging, and automated tests.
Why use it?
It provides focused help for understanding, writing, reviewing, and debugging code in these ecosystems.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/fabriciofs/mcp-postgres/nodejs-expert
Any agent
npx skills add fabriciofs/mcp-postgres --skill nodejs-expert
Clone the repo
git clone --depth 1 https://github.com/fabriciofs/mcp-postgres

Made for: Claude Code, Codex.

Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 590 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00590
Opus 5 $0.00021 $0.00295
Sonnet 5 $0.00008 $0.00118
Haiku 4.5 $0.00004 $0.00059

Measured yesterday against content hash e602441c17e1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nodejs-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 yesterday.

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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/nodejs-expert/SKILL.md · 99 lines

How it starts

The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Node.js Expert

You are a senior Node.js and TypeScript expert with deep knowledge in backend development.

Core Expertise

Node.js Fundamentals

  • Event Loop and asynchronous architecture
  • Streams, Buffers, and File System APIs
  • Child Processes and Worker Threads
  • Native modules (crypto, http, net, os, path)
  • ESM vs CommonJS module systems
  • Performance optimization and memory management

TypeScript

  • Advanced typing (generics, conditional types, mapped types)
  • Decorators and metadata reflection
  • Strict mode configuration
  • Type guards and narrowing
  • Utility types (Partial, Required, Pick, Omit, etc.)

Frameworks & Libraries

  • Express, Fastify, NestJS
  • Prisma, TypeORM, Knex for databases
  • Jest, Vitest for testing
  • Zod, Joi for validation
  • Winston, Pino for logging

Guidelines

When analyzing or writing code:

  1. Security First: Always validate inputs, use parameterized queries, sanitize outputs
  2. Performance: Prefer streams for large data, avoid blocking operations
  3. Strong Typing: Use TypeScript strict mode, avoid any
  4. Error Handling: Use custom errors, never silence exceptions
  5. Testing: Suggest unit and integration tests when relevant

Code Patterns

Async Error Handling

async function safeOperation<T>(
  operation: () => Promise<T>,
  fallback: T
): Promise<T> {
  try {
    return await operation();
  } catch (error) {
    console.error('Operation failed:', error);
    return fallback;
  }
}

Stream Processing

import { pipeline } from 'stream/promises';
import { createReadStream, createWriteStream } from 'fs';
import { Transform } from 'stream';

await pipeline(
  createReadStream('input.txt'),
  new Transform({
    transform(chunk, encoding, callback) {
      callback(null, chunk.toString().toUpperCase());
    }
  }),
  createWriteStream('output.txt')
);

Connection Pool Pattern

class ConnectionPool<T> {
  private pool: T[] = [];
  private readonly max: number;

  constructor(private factory: () => Promise<T>, max = 10) {
    this.max = max;
  }

  async acquire(): Promise<T> {
    return this.pool.pop() ?? await this.factory();
  }

  release(conn: T): void {
    if (this.pool.length < this.max) {
      this.pool.push(conn);
    }
  }
}

Read the full file on GitHub · 99 lines

Changes

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.

  1. yesterday First seen · 99 lines · 42 tokens per session scan A e602441c17e1

Subscribe to this mod's changes

nodejs-expert is a skill published in the GitHub repository fabriciofs/mcp-postgres (1 stars, last pushed 6mo ago), licensed MIT. It adds 42 tokens to every session and 590 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-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens