nest-best-practices

nest-best-practices is a skill for Claude Code from biggora/claude-plugins-registry. It costs 49 tokens per session (2,375 once invoked), scanned A, original, MIT.

A set of version-aware guidelines for developing, reviewing, testing, or migrating NestJS applications. NestJS is a framework for building server-side applications with JavaScript or TypeScript.

In plain words
What is it for?
Use it when changing NestJS modules, APIs, validation, transports, tests, configuration, or dependencies.
Why use it?
It helps changes match the project's installed NestJS version, module format, adapters, validation, and test setup.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the project-delivery-orchestrator plugin — 34 skills, 1 command, 5 agents shipped together

Good fit Use it when changing NestJS modules, APIs, validation, transports, tests, configuration, or dependencies.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/biggora/claude-plugins-registry/nest-best-practices
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.

Any agent
npx skills add biggora/claude-plugins-registry --skill nest-best-practices
Clone the repo
git clone --depth 1 https://github.com/biggora/claude-plugins-registry

Made for: Claude Code.

Or install project-delivery-orchestrator, the plugin that ships this one along with the rest of its 34 skills, 1 command, 5 agents.

Wrote 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.

agentmods badge for nest-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/nest-best-practices/github.svg)](https://agentmods.dev/skills/biggora/claude-plugins-registry/nest-best-practices)
Your own site
<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/nest-best-practices"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/nest-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.

agentmods 80×15 button for nest-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/skills/biggora/claude-plugins-registry/nest-best-practices"><img src="https://agentmods.dev/badge/skills/biggora/claude-plugins-registry/nest-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 49 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,375 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00049 $0.02375
Opus 5 $0.00024 $0.01188
Sonnet 5 $0.00010 $0.00475
Haiku 4.5 $0.00005 $0.00237

Measured 10d ago against content hash 844dc62c0275, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

nest-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 10d 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.

src/skills/nest-best-practices/SKILL.md · 137 lines

How it starts

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

NestJS Best Practices

Use the project's source, package manifest, lockfile, module format, HTTP adapter, and test runner as the primary context. Read only the references relevant to the task.

This skill targets NestJS 12. The npm latest tag for @nestjs/core was verified as 12.0.1 on 2026-08-29. Treat that patch number as a dated observation: re-check the registry and official documentation before recommending or performing an upgrade.

Version Gate

  1. Inspect package.json and the lockfile for @nestjs/core, @nestjs/common, platform adapters, CLI, and companion packages.
  2. Preserve the installed major for ordinary feature and bug-fix work. Do not introduce v12-only APIs into a v10/v11 project.
  3. For a new project or an explicit upgrade, verify the current stable npm tag and official migration guide. Keep all @nestjs/* packages on compatible majors.
  4. For v11 to v12 work, read NestJS 12 migration before editing dependencies or configuration.
  5. Preserve the project's CommonJS or ESM choice unless the user requests a module-format migration. Nest 12 packages are ESM, but supported CommonJS applications can consume them on compatible Node.js versions.

Working Method

  • Inspect existing module boundaries and nearby patterns before generating code.
  • Prefer framework primitives and the adapter already in use. Avoid Express-specific response handling in code that should remain adapter-independent.
  • Keep controllers thin: translate transport input/output and delegate business rules to providers.
  • Use explicit injection tokens for non-class dependencies. Export only providers that other modules actually consume.
  • Choose singleton scope by default; request scope has a performance and dependency-graph cost.
  • Validate untrusted input at the transport boundary. Use class-based or Standard Schema-based validation consistently with the project; do not layer both without a concrete reason.
  • Keep secrets and environment-specific values outside source. Validate configuration during startup.
  • Preserve stable error contracts. In Nest 12, prefer errorCode for machine decisions and messages for humans.
  • Test observable behavior through @nestjs/testing; preserve the repository's Jest or Vitest choice.
  • After edits, run the narrow relevant tests, type checking, linting, and build commands already defined by the repository.

Read the full file on GitHub · 137 lines

Files

What ships with it

60 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.

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. 10d ago First seen · 137 lines · 49 tokens per session scan A 844dc62c0275

Subscribe to this mod's changes

nest-best-practices is a skill published in the GitHub repository biggora/claude-plugins-registry (2 stars, last pushed 12d ago), licensed MIT. It adds 49 tokens to every session and 2,375 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

adapter-express

Mount tRPC as Express middleware with createExpressMiddleware() from @trpc/server/adapters/express. Access Express req/res in createContext via CreateExpressContextOptions. Mount at a path prefix like app.use('/trpc', ...). Avoid global express.json() conflicting with tRPC body parsing for FormData.

trpc/trpc · 67 tokens

trpc-router

Entry point for all tRPC skills. Decision tree routing by task: initTRPC.create(), t.router(), t.procedure, createTRPCClient, adapters, subscriptions, React Query, Next.js, links, middleware, validators, error handling, caching, FormData.

trpc/trpc · 59 tokens

stripe-projects

Use after E2B sandbox/API access has been provisioned through Stripe Projects and the user needs to use the resulting E2B API key with the E2B CLI, JavaScript SDK, Python SDK, or Code Interpreter SDK.

e2b-dev/E2B · 51 tokens

chat-sdk

Build multi-platform chat bots with Chat SDK (chat npm package). Use when developers want to (1) Build a Slack, Teams, Google Chat, Discord, Telegram, GitHub, Linear, or WhatsApp bot, (2) Use Chat SDK to handle mentions, direct messages, subscribed threads, reactions, slash commands, cards, modals, files, or AI…

vercel-labs/open-agents · 191 tokens

nestjs-expert

Creates and configures NestJS modules, controllers, services, DTOs, guards, and interceptors for enterprise-grade TypeScript backend applications. Use when building NestJS REST APIs or GraphQL services, implementing dependency injection, scaffolding modular architecture, adding JWT/Passport authentication, integrating…

Jeffallan/claude-skills · 107 tokens

fastify-best-practices

Guides development of Fastify Node.js backend servers and REST APIs using TypeScript or JavaScript. Use when building, configuring, or debugging a Fastify application — including defining routes, implementing plugins, setting up JSON Schema validation, handling errors, optimising performance, managing authentication…

mcollina/skills · 137 tokens