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 phuonghx/aim-cli --skill nodejs-best-practicesgit clone --depth 1 https://github.com/phuonghx/aim-cliWrote 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/phuonghx/aim-cli/nodejs-best-practices)<a href="https://agentmods.dev/skills/phuonghx/aim-cli/nodejs-best-practices"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/nodejs-best-practices/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/phuonghx/aim-cli/nodejs-best-practices"><img src="https://agentmods.dev/badge/skills/phuonghx/aim-cli/nodejs-best-practices.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.00086 | $0.01621 |
| Opus 5.5 | $0.00034 | $0.00648 |
| Sonnet 5.5 | $0.00017 | $0.00324 |
| Haiku 4.5 | $0.00009 | $0.00162 |
Grade A, and why
nodejs-best-practices 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js Backend Decisions
The aim here is judgment, not recipes. Identical projects rarely exist, so resist reaching for the same stack and layout every time. When the requirements leave a choice open, surface the trade-off and ask before committing.
Picking a framework
Start from where the code will run and how much structure the team needs, then narrow:
- Functions at the edge (Vercel, Cloudflare, Netlify) reward tiny footprints and fast cold starts -- reach for Hono.
- Throughput-sensitive HTTP services where every millisecond counts favor Fastify (its schema-driven serialization is a real edge; still measure against your own routes).
- Teams that want opinionated structure, dependency injection, and decorators out of the box lean toward NestJS.
- Brownfield systems or cases needing the widest middleware catalog stay on Express.
- A frontend already in play (Next.js) often makes route handlers or tRPC the path of least resistance.
Questions worth answering before you decide: Where does this deploy? Does cold-start latency show up in the SLO? What has the team shipped before? Is there existing code that constrains the choice?
Choosing the runtime layer
TypeScript without a build step. Recent Node LTS strips types from .ts files on the fly, so node server.ts runs directly. The catch: only erasable syntax works -- enum, runtime namespace, and constructor parameter properties will throw. When you need those, run through tsx instead. This is handy for one-off scripts and lean services.
Modules. New code should be ESM (import/export) -- it tree-shakes better and is the direction the ecosystem is moving. Stick with CommonJS (require) only when an existing codebase or a stubborn dependency forces it.
Which runtime. Node remains the safe default with the deepest ecosystem. Bun is worth a look when raw speed and an integrated toolchain matter; Deno appeals when you want TypeScript and a permissions model built in.
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 · 133 lines · 86 tokens per session scan A e3c7977edbb6
nodejs-best-practices is a skill published in the GitHub repository phuonghx/aim-cli (1 stars, last pushed 3mo ago), licensed MIT. It adds 86 tokens to every session and 1,621 once invoked, about $0.0003 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
node-modern
Use this skill when writing, reviewing, or refactoring Node.js code — modules, async flow, cancellation, file and process I/O, HTTP — on a current Node.js release. Triggers: user mentions "Node", "Node.js", "ESM", "CommonJS", "require", "import", "fetch", "AbortSignal", "AbortController", "stream", "childprocess"…
api-design
Use this skill when designing, implementing, or reviewing an HTTP API — endpoints, request and response shapes, errors, pagination, versioning, and authorization. Triggers: user says "API", "endpoint", "REST", "route", "status code", "pagination", "request body", "response shape", "OpenAPI", "versioning"…
configure-server
Configures how the MCP Task Orchestrator SERVER runs and is reached — transport (HTTP vs STDIO), the REST API, port publishing, config mounts, and config-sync. Use when a user says: run the server, register the image, set up the Docker container, enable the REST API, set up config-sync, reconfigure the server, change…
nextjs-modern
Build, migrate, and debug Next.js 16 App Router applications with React 19, Server Components, Server Actions, explicit caching, and production deployment. Use when implementing Next.js routes, upgrading to the latest stable Next.js, or fixing rendering and cache behavior.
authentication-sessions
Implement application sign-in, sessions and identity integration with explicit account/tenant authorization. Use when building OAuth/OIDC, passkeys, password login or session renewal; use security-scanner for a requested defensive review.
cloudflare-workers
Build and maintain Cloudflare Workers with typed bindings, explicit compatibility and isolated validation. Use when implementing Workers handlers, integrating KV/R2/D1/Durable Objects/Queues or configuring Wrangler; deployment remains governed by the user task and target environment.