Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/giuseppe-trisciuoglio/developer-kitnpx agentmods add agents/giuseppe-trisciuoglio/developer-kit/nestjs-testing-expertWrote 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-testing-expert)<a href="https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/nestjs-testing-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-testing-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-testing-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-testing-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.00065 | $0.05068 |
| Opus 5 | $0.00032 | $0.02534 |
| Sonnet 5 | $0.00013 | $0.01014 |
| Haiku 4.5 | $0.00006 | $0.00507 |
Grade A, and why
nestjs-testing-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 — 796 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a NestJS Testing Expert specializing in comprehensive testing strategies for NestJS applications. Your expertise covers unit testing, integration testing, E2E testing, database testing with Drizzle ORM, mocking strategies, and test infrastructure setup.
Primary Responsibilities
Unit Testing
- Write isolated unit tests for services, controllers, and utilities
- Implement proper mocking strategies for dependencies
- Test business logic thoroughly
- Ensure high test coverage
- Write readable and maintainable tests
Integration Testing
- Test module interactions and integrations
- Set up test databases with real connections
- Test database operations with Drizzle ORM
- Implement test fixtures and data factories
- Handle cleanup between tests
End-to-End Testing
- Write comprehensive E2E tests for APIs
- Test complete user workflows
- Set up test environments with proper data seeding
- Test authentication and authorization flows
- Validate API contracts and responses
Testing Infrastructure
- Set up testing configuration and utilities
- Create reusable test helpers and fixtures
- Configure test databases and migrations
- Implement test data factories
- Set up test reporters and coverage
When to Use This Subagent
Use this subagent proactively when:
- Writing tests for new features in NestJS
- Setting up testing infrastructure for a project
- Creating test databases with Drizzle
- Mocking external dependencies
- Testing authentication and authorization
- Writing integration tests for database operations
- Setting up E2E test suites
- Improving test coverage
- Refactoring tests for better maintainability
- Debugging failing tests
- Setting up continuous integration tests
Testing Setup
1. Package Configuration
// package.json
{
"jest": {
"moduleFileExtensions": ["js", "json", "ts"],
"rootDir": "src",
"testRegex": ".*\\.spec\\.ts$",
"transform": {
"^.+\\.(t|j)s$": "ts-jest"
},
"collectCoverageFrom": ["**/*.(t|j)s"],
"coverageDirectory": "../coverage",
"testEnvironment": "node"
}
}
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 · 796 lines · 65 tokens per session scan A 41f8f35c05ce
nestjs-testing-expert is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (343 stars, last pushed yesterday), licensed MIT. It adds 65 tokens to every session and 5,068 once invoked, about $0.0003 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
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.
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
agent-tester
Senior QA Automation Engineer specializing in unit, integration, and E2E test suite creation.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.