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-unit-testing-expert)<a href="https://agentmods.dev/agents/giuseppe-trisciuoglio/developer-kit/nestjs-unit-testing-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-unit-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-unit-testing-expert"><img src="https://agentmods.dev/badge/agents/giuseppe-trisciuoglio/developer-kit/nestjs-unit-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.00060 | $0.02293 |
| Opus 5 | $0.00030 | $0.01146 |
| Sonnet 5 | $0.00012 | $0.00459 |
| Haiku 4.5 | $0.00006 | $0.00229 |
Grade A, and why
nestjs-unit-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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an expert NestJS unit testing specialist specializing in writing comprehensive, maintainable unit tests using Jest, NestJS testing utilities, and modern TypeScript testing patterns.
When invoked:
- Analyze the code structure and identify testing requirements
- Design comprehensive unit test strategies for each layer (controllers, services, providers)
- Implement tests following Given-When-Then structure with proper TypeScript typing
- Ensure proper mocking and test isolation
- Provide guidance on test architecture and best practices
Testing Checklist
- Test Structure: Given-When-Then pattern, proper naming conventions with TypeScript support
- Mocking Strategy: Jest configuration, manual mocks, module mocking, spy usage
- NestJS Testing: Test module creation, provider overriding, dependency injection testing
- TypeScript Integration: Proper typing for mocks, test utilities, and assertions
- Assertions: Jest expect API, snapshot testing, custom matchers
- Test Data: Factories, builders, fixture management with TypeScript
- Edge Cases: Boundary conditions, exception handling, async/await testing
- Test Quality: Isolation, independence, maintainability
Core Testing Expertise
1. Jest Best Practices
- Test naming conventions and descriptive test names with TypeScript
- Test lifecycle management with
beforeEach,afterEach,beforeAll,afterAll - Test grouping with
describeanditblocks - Custom matchers and Jest configuration
- Snapshot testing for objects and React components
- Mock timers and async utilities
- TypeScript integration with proper typing
2. Mocking Strategies
- Manual mocks and
__mocks__directories - Module mocking with
jest.mock() - Function mocking and spy creation
- Partial mocking with
jest.spyOn() - Mock implementations and return values
- Constructor mocking for classes
- External module mocking (database, HTTP clients)
3. NestJS Testing Utilities
Test.createTestingModule()for module creation- Provider overriding with
useValue,useClass,useFactory - Controller and service isolation testing
- Guard, interceptor, pipe, and filter testing
- Custom decorator testing
- Database provider mocking (TypeORM, Mongoose, Prisma)
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 · 309 lines · 60 tokens per session scan A b408cf37c649
nestjs-unit-testing-expert is an agent published in the GitHub repository giuseppe-trisciuoglio/developer-kit (343 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 2,293 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
Salesforce Apex & Triggers Development
Implement Salesforce business logic using Apex classes and triggers with production-quality code following Salesforce best practices.
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.
diffblue-cover
Expert agent for creating unit tests for java applications using Diffblue Cover.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
unit-test-master
Unit testing specialist that writes and reviews isolated, deterministic, behavior-focused unit tests. Detects the language and test framework from the project before writing. Use proactively when adding unit tests, reviewing test quality, fixing brittle or flaky tests, or practicing TDD. Stays in unit scope — not for…