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 DDS-Solutions/AI-TadPole-OS --skill nodejs-best-practicesgit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/nodejs-best-practices)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/nodejs-best-practices"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/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/dds-solutions/ai-tadpole-os/nodejs-best-practices"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/nodejs-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.01236 |
| Opus 5.5 | $0.00013 | $0.00494 |
| Sonnet 5.5 | $0.00007 | $0.00247 |
| Haiku 4.5 | $0.00003 | $0.00124 |
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 12d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / nodejs-best-practices
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Event loop stalling, unvalidated boundary schemas, or blocking synchronous file I/O.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Node.js Best Practices & Architecture Protocol
Philosophy: Asynchronous by default, resilient to event-loop blocking, strictly typed at boundaries.
Core Principle: Think in streams and non-blocking concurrency; offload CPU-heavy computation to worker threads.
Workflow Bindings: Integrated into/createand/refactor.
🎯 Progressive Disclosure & L3 Reference Index
Read the core Sovereign rules below; consult deep L3 Reference Guides on demand:
| L3 Reference Guide | Purpose | Trigger / When to Load |
|---|---|---|
references/runtime_patterns.md |
Framework benchmarks (Hono/Fastify/Nest), Zod schemas, threadpools | Framework selection & worker thread setup |
scripts/node_auditor.py |
Automated static auditor detecting blocking sync calls (*Sync) in event loop paths |
Auditing backend handler and service code |
🧭 1. Framework & Runtime Selection
What are you building?
├── Edge / Serverless / Modern REST ➔ Hono (Ultra-light, native TS)
├── High-Throughput Microservice ➔ Fastify (Fast JSON schema serializer)
├── Enterprise Structured App ➔ NestJS (Dependency injection, modular)
└── Full-stack Integration ➔ Next.js Server Actions / tRPC
🏛️ 2. Clean Layered Architecture
[Controller / Route] ➔ Validates request payload at the boundary (Zod/Valibot)
│
▼
[Service Layer] ➔ Encapsulates pure business logic (framework-agnostic)
│
▼
[Repository Layer] ➔ Performs database operations & external API I/O
What ships with it
2 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.
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.
- 12d ago Changed · +28 lines df4d01a1c9fa
- 1mo ago First seen · 78 lines · 33 tokens per session scan A 7b0ed549c849
nodejs-best-practices is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 1,236 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
nextjs-app-router
Full end-to-end tRPC setup for Next.js App Router. Covers route handler with fetchRequestHandler (GET + POST exports), TRPCProvider with QueryClientProvider, createTRPCOptionsProxy for RSC prefetching, HydrateClient/HydrationBoundary for hydration, useSuspenseQuery for Suspense, and server-side callers.
nextjs-pages-router
Set up tRPC in Next.js Pages Router with createNextApiHandler, createTRPCNext, withTRPC HOC, SSR via ssr option and ssrPrepass, SSG via createServerSideHelpers with getStaticProps, and server-side helpers for getServerSideProps prefetching.
server-setup
Initialize tRPC with initTRPC.create(), define routers with t.router(), create procedures with .query()/.mutation()/.subscription(), configure context with createContext(), export AppRouter type, merge routers with t.mergeRouters(), lazy-load routers with lazy().
subscriptions
Set up real-time event streams with async generator subscriptions using .subscription(async function() { yield }). SSE via httpSubscriptionLink is recommended over WebSocket. Use tracked(id, data) from @trpc/server for reconnection recovery with lastEventId. WebSocket via wsLink and createWSClient from @trpc/client…
client-setup
Create a vanilla tRPC client with createTRPCClient (), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typing.
links
Configure the tRPC client link chain: httpLink, httpBatchLink, httpBatchStreamLink, splitLink, loggerLink, wsLink, createWSClient, httpSubscriptionLink, unstablelocalLink, retryLink. Choose the right terminating link. Route subscriptions via splitLink. Build custom links for SOA routing. Link options: url, headers…