Borrowing it
Nothing to install: this file belongs to hamzaali81/nestjs-agent-workflow-kit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hamzaali81/nestjs-agent-workflow-kit/main/.agents/skills/nestjs-developer/SKILL.mdgit clone --depth 1 https://github.com/hamzaali81/nestjs-agent-workflow-kitWrote 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/hamzaali81/nestjs-agent-workflow-kit/nestjs-developer)<a href="https://agentmods.dev/skills/hamzaali81/nestjs-agent-workflow-kit/nestjs-developer"><img src="https://agentmods.dev/badge/skills/hamzaali81/nestjs-agent-workflow-kit/nestjs-developer.svg" alt="Measured on agentmods" 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.00080 | $0.01008 |
| Opus 5 | $0.00040 | $0.00504 |
| Sonnet 5 | $0.00016 | $0.00202 |
| Haiku 4.5 | $0.00008 | $0.00101 |
Grade A, and why
nestjs-developer 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 6d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
NestJS Developer Guidelines
- Always determine the project's NestJS major version and package manager before generating code; APIs and defaults vary between v9/v10/v11. Read
package.json. - Follow the framework conventions and the project's
docs/standards/rules. Use the Nest CLI (nest generate) to scaffold modules, controllers, services, guards, etc. so structure stays consistent. - After generating code, run
npm run build(ornest build) and the linter. Fix type and lint errors before finishing—do not leave a broken build.
Creating new projects
If the user has not specified otherwise:
- Scaffold with the Nest CLI:
npx @nestjs/cli new <project-name>(or a pinned version@nestjs/cli@<v>). Ask which package manager if it matters; default to the repo's existing one. - Enable strict TypeScript, the global
ValidationPipe,ConfigModulewith env validation, and aPrismaModuleunless the user chose a different data layer. - See
nestjs-new-appfor the full new-app checklist and bootstrap wiring.
Core mental model
- Modules compose the app and define DI scope. Controllers are the transport layer. Providers/services hold business logic. Repositories /
PrismaServiceown persistence. - Cross-cutting behavior is expressed as pipes (validation/transform), guards (authz), interceptors (response/logging/caching), and exception filters (error shaping)—registered per-handler, per-controller, or globally via
APP_*providers. - Everything is wired through dependency injection; use constructor injection with
private readonly.
Generation rules
- Every request body/query/param object is a class DTO validated by class-validator. No plain interfaces for validated input. See
references/dtos-validation.md. - Controllers stay thin: extract input → call one service method → return. Push logic into services. See
references/controllers-routing.md. - Services do the work; inject repositories/other services. Keep transport concerns out. See
references/providers-di.md. - Read config through a typed
ConfigService, neverprocess.envin feature code. Seereferences/configuration.md. - Data access goes through
PrismaService/repositories, never controllers. Seeprisma-data-layer. - Errors are thrown as
HttpExceptionsubclasses and shaped by a global filter. Seereferences/error-handling.md. - Document endpoints and DTOs for OpenAPI. See
openapi-swagger. - Write Jest unit tests (mock collaborators) and Supertest E2E tests (real request path with global pipes/filters). See
references/testing.md.
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.
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.
- 6d ago First seen · 62 lines · 80 tokens per session scan A a77f73abcc2c
nestjs-developer is a skill published in the GitHub repository hamzaali81/nestjs-agent-workflow-kit (2 stars, last pushed 1mo ago), licensed MIT. It adds 80 tokens to every session and 1,008 once invoked, about $0.0004 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
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-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.
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.
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…
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…
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…