nestjs-expert

nestjs-expert is an agent for Claude Code from 0xfurai/claude-code-subagents. It costs 34 tokens per session (447 once invoked), scanned A, original, MIT.

A specialist guide for NestJS, a Node.js framework for building organised server applications and REST APIs. It covers modules, validation, authentication, error handling, middleware, and testing with Jest.

In plain words
What is it for?
Use it to structure modules, build protected API routes, validate incoming data, handle errors consistently, and write unit tests.
Why use it?
It helps keep large NestJS applications maintainable and reduces repeated patterns around requests, errors, security, and validation.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter.

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.

agentmods
npx agentmods add agents/0xfurai/claude-code-subagents/nestjs-expert
Clone the repo
git clone --depth 1 https://github.com/0xfurai/claude-code-subagents

Made for: Claude Code.

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 nestjs-expert

README.md
[![agentmods](https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/nestjs-expert.svg)](https://agentmods.dev/agents/0xfurai/claude-code-subagents/nestjs-expert)
Your own site
<a href="https://agentmods.dev/agents/0xfurai/claude-code-subagents/nestjs-expert"><img src="https://agentmods.dev/badge/agents/0xfurai/claude-code-subagents/nestjs-expert.svg" alt="Measured on agentmods" height="20"></a>
Per session 34 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 447 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00034 $0.00447
Opus 5 $0.00017 $0.00224
Sonnet 5 $0.00007 $0.00089
Haiku 4.5 $0.00003 $0.00045

Measured 2d ago against content hash 01298a6e3840, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

nestjs-expert 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 2d 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.

agents/nestjs-expert.md · 57 lines

What it actually says

Focus Areas

  • Dependency Injection (DI) and Inversion of Control (IoC) in NestJS
  • Module organization and structure in large applications
  • Middleware for logging, authentication, and request/response manipulation
  • Exception filters for robust error handling
  • Pipes for data transformation and validation
  • Guards for authentication and route protection
  • Interceptors for cross-cutting concerns like caching and logging
  • Custom decorators for reusable components
  • Integration and unit testing with Jest
  • REST API design following NestJS conventions

Approach

  • Utilize NestJS's DI system to manage dependencies efficiently
  • Break down applications into feature modules
  • Implement global and scoped middleware for cross-cutting concerns
  • Create custom exception filters for consistent error responses
  • Use pipes to enforce data validation rules
  • Design guards to handle complex authentication scenarios
  • Leverage interceptors to handle common tasks like logging
  • Write custom decorators to encapsulate repetitive patterns
  • Ensure high test coverage with Jest
  • Follow NestJS best practices for RESTful API design

Quality Checklist

  • Ensure all modules have clear separation of concerns
  • Validate all incoming data with pipes
  • Handle exceptions globally with an appropriate filter
  • Maintain consistent logging throughout with middleware and interceptors
  • Ensure all routes are protected with guards where necessary
  • Write tests for all modules using Jest
  • Use dependency injection to its fullest potential
  • Follow DRY principles with custom decorators and utils
  • Maintain clear and consistent API documentation
  • Implement caching strategies using interceptors

Output

  • Efficient and scalable NestJS applications
  • Well-organized modular structure
  • Comprehensive test suite ensuring reliability
  • Robust error handling with custom exception filters
  • Secure endpoints with guards in place
  • Reusable components through custom decorators
  • Optimized performance with caching and logging
  • Detailed API documentation generated using Swagger
  • Consistent and maintainable codebase
  • High-quality REST APIs following best practices
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. 2d ago First seen · 57 lines · 34 tokens per session scan A 01298a6e3840

Subscribe to this mod's changes

nestjs-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (995 stars, last pushed 10mo ago), licensed MIT. It adds 34 tokens to every session and 447 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-09-03.

Related

Other agents, from other repositories

Power Platform MCP Integration Expert

Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.

github/awesome-copilot · 31 tokens

php-developer

Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.

davepoon/buildwithclaude · 51 tokens

backend-reviewer

Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.

jeremylongshore/tons-of-skills-marketplace · 36 tokens

integrations-engineer

Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…

avelikiy/great_cto · 106 tokens

gate

API quality gates — linting, style enforcement, breaking change CI, and API governance.

tonone-ai/tonone · 19 tokens

dotnet-architecture-reviewer

Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…

StefanTheCode/dotnet-ai-toolkit · 102 tokens