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 dkmqflx/nestjs-best-practices-plugin --skill nestjs-validation-pipesgit clone --depth 1 https://github.com/dkmqflx/nestjs-best-practices-pluginWrote 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/dkmqflx/nestjs-best-practices-plugin/nestjs-validation-pipes)<a href="https://agentmods.dev/skills/dkmqflx/nestjs-best-practices-plugin/nestjs-validation-pipes"><img src="https://agentmods.dev/badge/skills/dkmqflx/nestjs-best-practices-plugin/nestjs-validation-pipes/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/dkmqflx/nestjs-best-practices-plugin/nestjs-validation-pipes"><img src="https://agentmods.dev/badge/skills/dkmqflx/nestjs-best-practices-plugin/nestjs-validation-pipes.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.00062 | $0.00483 |
| Opus 5 | $0.00031 | $0.00242 |
| Sonnet 5 | $0.00012 | $0.00097 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
nestjs-validation-pipes 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.
What it actually says
NestJS Validation & Pipes
Pipes run before route handlers to validate and transform incoming request data. Combined with class-validator and class-transformer, they keep DTOs the single source of truth for input shape and constraints.
When to Apply
- Validating request bodies, query params, or route params in a NestJS app.
- Configuring
ValidationPipe(globally or per-route). - Annotating DTOs with
class-validatordecorators. - Coercing param types with built-in parse pipes (
ParseIntPipe,ParseUUIDPipe, ...). - Writing a reusable custom pipe via
PipeTransform.
Rules
global-validation-pipe- RegisterValidationPipeonce inmain.tsso every endpoint is validated.whitelist-strip-unknown- Usewhitelist+forbidNonWhitelistedto strip or reject unexpected properties.transform-payloads- Enabletransform: trueto auto-instantiate DTO classes and coerce primitive types.dto-classes-not-interfaces- Define DTOs as classes; interfaces are erased at runtime and carry no metadata.class-validator-decorators- Annotate every DTO field withclass-validatordecorators.nested-object-validation- Use@ValidateNested+@Typeto validate nested DTOs and arrays.built-in-parse-pipes- UseParseIntPipe/ParseUUIDPipe/ParseBoolPipeto coerce and validate params.custom-pipe-implementation- ImplementPipeTransformfor reusable custom validation or transformation.
How to Use
Read the relevant file under rules/ for the topic at hand. Each rule states why it matters and shows an incorrect vs. correct example. Apply them when writing or reviewing NestJS input-handling code.
What ships with it
8 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/built-in-parse-pipes.md 842 B
- rules/class-validator-decorators.md 744 B
- rules/custom-pipe-implementation.md 1.1 KB
- rules/dto-classes-not-interfaces.md 732 B
- rules/global-validation-pipe.md 732 B
- rules/nested-object-validation.md 849 B
- rules/transform-payloads.md 801 B
- rules/whitelist-strip-unknown.md 673 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.
- 12d ago First seen · 36 lines · 62 tokens per session scan A 6c1ec947989e
nestjs-validation-pipes is a skill published in the GitHub repository dkmqflx/nestjs-best-practices-plugin (1 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 483 once invoked, about $0.0003 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.
Other skills, from other repositories
better-auth
Skill for integrating Better Auth - comprehensive TypeScript authentication framework for Cloudflare D1, Next.js, Nuxt, and 15+ frameworks. Use when adding auth, encountering D1 adapter errors, or implementing OAuth/2FA/RBAC features.
nodejs-backend
Node.js backend patterns: layered architecture, TypeScript, validation, error handling, security, observability, logging, metrics, deployment. Use when building REST APIs, REST endpoints, middleware, Express/Fastify/Hono/NestJS/Koa servers, tRPC procedures, Bun servers, or server-side TypeScript.
node-patterns
Use when writing Node.js/TypeScript backend code — Express, Fastify, or NestJS services, APIs, workers. Builder playbook: project layout, async discipline, typed config, error taxonomy, DI boundaries, testing shape. Complements typescript-reviewer (this prevents, the reviewer catches).
fastapi-best-practices
Use when writing, reviewing, or refactoring FastAPI code — endpoints, APIRouter, query/path parameters, dependencies (Depends), Pydantic request/response models, error handling, async def vs def, lifespan events, streaming, background tasks, settings, middleware, or CORS. Triggers on FastAPI backend work, route…
feathers-service
Scaffold or extend a FeathersJS v5 (Dove) service using the idiomatic four-file pattern ( .ts, .class.ts, .schema.ts, .shared.ts), register it with app.configure, and wire it into the ServiceTypes declaration. Use this whenever the user wants to add a new resource, endpoint, collection, table-backed CRUD service, or…
backend-dev-guidelines
Opinionated backend development standards for Node.js + Express + TypeScript microservices. Covers layered architecture, BaseController pattern, dependency injection, Prisma repositories, Zod validation, unifiedConfig, Sentry error tracking, async safety, and testing discipline.