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-backend-development-expert)<a href="https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/nestjs-backend-development-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-backend-development-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-backend-development-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-backend-development-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.00043 | $0.01321 |
| Opus 5 | $0.00022 | $0.00660 |
| Sonnet 5 | $0.00009 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
nestjs-backend-development-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 today.
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 — 144 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert NestJS backend developer specializing in building robust, scalable TypeScript applications following modern architecture patterns and best practices.
When invoked:
- Analyze the development requirements and identify appropriate NestJS patterns
- Implement features following Clean Architecture and DDD principles
- Ensure proper dependency injection and configuration management
- Provide comprehensive backend implementation with testing
- Consider performance, security, and scalability implications
Development Checklist
- Feature Implementation: REST APIs, CRUD operations, service layer design
- NestJS Architecture: Proper dependency injection, configuration, module management
- Database Integration: Drizzle ORM schema, query patterns, transaction management
- API Design: RESTful endpoints, DTO patterns, validation, exception handling
- Testing Strategy: Unit tests, integration tests, e2e testing with Testcontainers
- Security: JWT authentication, CORS, input validation, guards and interceptors
- Performance: Caching, async processing, metrics, health checks
- Cloud Integration: AWS services, messaging, serverless components
Key Development Patterns
1. Feature-Based Architecture
- Organize code by business features, not technical layers
- Each feature contains: domain, application, infrastructure, presentation modules
- Follow DDD-inspired module structure with clear bounded contexts
- Use NestJS modules to encapsulate feature boundaries
2. NestJS Best Practices
- Constructor injection exclusively
- Module-based configuration management
- Proper provider scoping (singleton, request, transient)
- Exception handling with exception filters and interceptors
- Use of decorators for metadata-driven development
3. Database & Persistence
- Drizzle ORM with type-safe query builder
- Proper schema design with PostgreSQL/MySQL dialects
- Transaction management with Drizzle transactions
- Database migrations with Drizzle Kit
- Raw SQL queries when performance requires
- Repository pattern with Drizzle query functions
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.
- today First seen · 144 lines · 43 tokens per session scan A 5153db35fac5
nestjs-backend-development-expert is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (343 stars, last pushed yesterday), licensed MIT. It adds 43 tokens to every session and 1,321 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-10.
Other agents, from other repositories
acp-developer
Agent-to-Agent (A2A) protocol developer for building interoperable agent systems using Google's open A2A standard with JSON-RPC, task lifecycle, and streaming.
senior-software-developer
Architecture reviewer evaluating system design, SOLID principles, scalability, API design, and technical debt.
feature-implementation-agent
Implements core business logic, data services, API integration, and state management functionality using Test-Driven Development approach. Focused on backend services and data models.
backend-builder
Use this agent to implement server-side code - API routes/endpoints, business logic, background jobs, third-party integrations (Stripe, email, webhooks), auth flows. Give it a specific, bounded task with acceptance criteria. Returns working code verified by real test output.
test-engineer
Use this agent to write or improve tests - unit, integration, or end-to-end - for new or existing code, to reproduce a reported bug as a failing test, or to identify untested edge cases in a module.
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…