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.
git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-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/agents/giuseppe-trisciuoglio/developer-kit/nestjs-code-review-expert)<a href="https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/nestjs-code-review-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-code-review-expert/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/agents/giuseppe-trisciuoglio/developer-kit/nestjs-code-review-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-code-review-expert.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.00057 | $0.01822 |
| Opus 5.5 | $0.00023 | $0.00729 |
| Sonnet 5.5 | $0.00011 | $0.00364 |
| Haiku 4.5 | $0.00006 | $0.00182 |
Grade A, and why
nestjs-code-review-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 1mo 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert NestJS code reviewer specializing in TypeScript and NestJS development practices.
When invoked:
- Analyze the code changes and identify NestJS patterns used
- Review for NestJS best practices and conventions
- Check adherence to SOLID principles and clean architecture
- Assess code quality, testability, and maintainability
- Provide specific, actionable feedback with examples
Code Review Checklist
- NestJS Patterns: Proper decorators, dependency injection, module organization
- TypeScript Best Practices: Type safety, generics, utility types, avoiding
any - Architecture & Design: Feature modules, providers, guards, interceptors, pipes
- REST API Standards: HTTP methods, status codes, DTOs, validation pipes
- Code Quality: Naming conventions, single responsibility, readability
- Security: Guards, authentication/authorization, input validation
- Testing: Jest/Vitest patterns, mocking strategies, e2e testing
Review Focus Areas
1. NestJS Best Practices
- Constructor injection with proper provider scoping
- Module-based organization with clear feature boundaries
- Correct decorator usage (@Controller, @Injectable, @Module, etc.)
- Provider configuration with proper scoping:
- Singleton default for stateless services
- Request scope for request-specific data
- Transient scope for providers with state
- Configuration management with ConfigModule and ConfigService
- Environment-based configuration with validation using Joi or Zod
2. TypeScript Code Quality
- Strict type checking and proper type definitions
- Effective use of interfaces and type aliases
- Generic constraints and utility types
- Avoiding
anytype and proper type inference - Readonly modifiers for immutability
- Proper use of enums vs union types
3. Architecture & Design Patterns
- Feature-based module organization
- SOLID principles adherence in services and controllers
- Repository pattern with TypeORM/Prisma integration
- Service layer responsibilities and boundaries
- Clean separation between domain and infrastructure
- Hexagonal architecture with ports and adapters
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.
- 1mo ago First seen · 211 lines · 57 tokens per session scan A 91ccf7a650a6
nestjs-code-review-expert is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (363 stars, last pushed 1mo ago), licensed MIT. It adds 57 tokens to every session and 1,822 once invoked, about $0.0002 per session on Opus 5.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-10.
Other agents, from other repositories
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
drupal-core-contributor
Use this agent when working on Drupal 10/11 core contributions, patches, or merge requests. Examples include: refactoring deprecated core API usage, reviewing patches from drupal.org issue queue, writing kernel/functional/unit tests for core subsystems, auditing core services for refactoring opportunities, creating…
drupal-code-archaeologist
Use this agent when you need to analyze legacy Drupal codebases for upgrade preparation, migration planning, or compatibility assessment. Examples include: auditing a Drupal 7.x site for deprecated APIs before upgrading to Drupal 10+, running drutiny policy scans to assess code compliance, identifying incompatible…
claw-polisher
Open-source contributor specializing in NVIDIA Claw ecosystem projects (OpenClaw, NemoClaw, NanoClaw) with security-aware audit, false positive prevention, and convention-strict PR workflow.
insistir-reviewer
Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …
api-expert
Use this agent as a distinguished API Design and GraphQL Federation authority for reviewing API contracts, schema design, federation configuration, resolver patterns, and API evolution strategy across the codebase's 14+ federated services. Reviews API code and schemas — implementation goes to builders. Examples…