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 agentmods add agents/0xfurai/claude-code-subagents/nestjs-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWrote 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/agents/0xfurai/claude-code-subagents/nestjs-expert)<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>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.00034 | $0.00447 |
| Opus 5 | $0.00017 | $0.00224 |
| Sonnet 5 | $0.00007 | $0.00089 |
| Haiku 4.5 | $0.00003 | $0.00045 |
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.
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
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.
- 2d ago First seen · 57 lines · 34 tokens per session scan A 01298a6e3840
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.
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.
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.
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.
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…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
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…