Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ushibo/brigadenpx agentmods add skills/ushibo/brigade/nodejs-coreWrote 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/ushibo/brigade/nodejs-core)<a href="https://agentmods.dev/skills/ushibo/brigade/nodejs-core"><img src="https://agentmods.dev/badge/skills/ushibo/brigade/nodejs-core/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/ushibo/brigade/nodejs-core"><img src="https://agentmods.dev/badge/skills/ushibo/brigade/nodejs-core.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.00108 | $0.01956 |
| Opus 5.5 | $0.00043 | $0.00782 |
| Sonnet 5.5 | $0.00022 | $0.00391 |
| Haiku 4.5 | $0.00011 | $0.00196 |
Grade A, and why
nodejs-core 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
Use this skill when you need deep Node.js internals expertise, including:
- C++ addon development
- V8 engine debugging
- libuv event loop issues
- Build system problems
- Compilation failures
- Performance optimization at the engine level
- Understanding Node.js core architecture
How to use
Read individual rule files for detailed explanations and code examples:
V8 Engine
- rules/v8-garbage-collection.md - Scavenger, Mark-Sweep, Mark-Compact, generational GC
- rules/v8-hidden-classes.md - Hidden classes, inline caching, optimization
- rules/v8-jit-compilation.md - TurboFan, optimization/deoptimization patterns
libuv
- rules/libuv-event-loop.md - Event loop phases, timers, I/O, idle, check, close
- rules/libuv-thread-pool.md - Thread pool size, blocking operations, UV_THREADPOOL_SIZE
- rules/libuv-async-io.md - Async I/O patterns, handles, requests
Native Addons
- rules/napi.md - N-API development, ABI stability, async workers
- rules/node-addon-api.md - C++ wrapper patterns, best practices
- rules/native-memory.md - Buffer handling, external memory, prevent leaks
Core Modules Internals
- rules/streams-internals.md - How Node.js streams work at C++ level
- rules/net-internals.md - TCP/UDP implementation, socket handling
- rules/fs-internals.md - libuv fs operations, sync vs async
- rules/crypto-internals.md - OpenSSL integration, performance considerations
- rules/child-process-internals.md - IPC, spawn, fork implementation
- rules/worker-threads-internals.md - SharedArrayBuffer, Atomics, MessageChannel
What ships with it
27 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.
- rules/build-and-test-workflow.md 10 KB
- rules/build-system.md 7.6 KB
- rules/child-process-internals.md 12 KB
- rules/cli-options.md 15 KB
- rules/commit-messages.md 2.5 KB
- rules/configure.md 5.1 KB
- rules/contributing.md 8.5 KB
- rules/crypto-internals.md 12 KB
- rules/debugging-native.md 7.9 KB
- rules/fs-internals.md 10 KB
- rules/libuv-async-io.md 11 KB
- rules/libuv-event-loop.md 11 KB
- rules/libuv-thread-pool.md 10 KB
- rules/memory-debugging.md 12 KB
- rules/napi.md 14 KB
- rules/native-memory.md 12 KB
- rules/net-internals.md 14 KB
- rules/node-addon-api.md 15 KB
- rules/primordials.md 13 KB
- rules/profiling-v8.md 9.8 KB
- rules/reviewing-prs.md 11 KB
- rules/streams-internals.md 12 KB
- rules/v8-garbage-collection.md 11 KB
- rules/v8-hidden-classes.md 9.2 KB
- rules/v8-jit-compilation.md 10 KB
- rules/worker-threads-internals.md 13 KB
- tile.json 615 B
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 · 153 lines · 108 tokens per session scan A 3ee0d850a920
nodejs-core is a skill published in the GitHub repository ushibo/brigade (1 stars, last pushed 3mo ago), licensed MIT. It adds 108 tokens to every session and 1,956 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
nodejs-expert
Use when writing or debugging Node.js code — async/await pitfalls (forEach not awaiting, unhandled promise rejections), Express/NestJS/Fastify patterns and error-handler setup, package.json/npm/middleware issues, event loop and stream backpressure, ESM dirname gaps, or choosing between Express/NestJS/Fastify…
dev-team-node
Coordinates Node.js/TypeScript development (Next.js, NestJS, Vite, Express) with a team of specialized agents and inline quality gates. Use for multi-step Node.js tasks that need decomposition and multi-agent coordination.
dev-team-python
Coordinates Python development (Django, Flask, FastAPI) with a team of specialized agents and inline quality gates. Use for multi-step Python tasks that need decomposition and multi-agent coordination.
node-backend
Node.js backend development patterns for Express, NestJS, Fastify, and Hono. Use when implementing APIs, authentication, middleware, services, and server-side logic with Node.js and TypeScript. Provides project structure, code patterns, and best practices.
nest-best-practices
NestJS framework best practices and production patterns. Use whenever working with NestJS — creating modules, controllers, services, DTOs, guards, interceptors, pipes, middleware, or building REST/GraphQL/microservice APIs. Also use when setting up authentication, authorization, validation, queues, health checks…
django-expert
Expert Django backend development guidance. Use when creating Django models, views, serializers, or APIs; debugging ORM queries or migrations; optimizing database performance; implementing authentication; writing tests; or working with Django REST Framework. Follows Django best practices and modern patterns.