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 rules/holtwood/awesome-cursorrules-zh/nestjs-testing-guidelinesgit clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zhWrote 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/rules/holtwood/awesome-cursorrules-zh/nestjs-testing-guidelines)<a href="https://agentmods.dev/rules/holtwood/awesome-cursorrules-zh/nestjs-testing-guidelines"><img src="https://agentmods.dev/badge/rules/holtwood/awesome-cursorrules-zh/nestjs-testing-guidelines.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.00089 | $0.00089 |
| Opus 5 | $0.00044 | $0.00044 |
| Sonnet 5 | $0.00018 | $0.00018 |
| Haiku 4.5 | $0.00009 | $0.00009 |
Grade A, and why
nestjs-testing-guidelines 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 6d 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
- 使用标准的 Jest 框架进行测试。
- 为每个控制器和服务编写测试。
- 为每个 api 模块编写端到端测试。
- 为每个控制器添加 admin/test 方法作为冒烟测试。
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.
- 6d ago First seen · 9 lines · 89 tokens per session scan A 513a6e8cac5f
nestjs-testing-guidelines is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (232 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session, about $0.0004 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-08-30.
Other cursor rules, from other repositories
page-object-patterns
Page Object Model patterns for Selenium — BasePage, component objects, and fluent interfaces.
testing-fundamentals
Core Cypress testing principles — selector strategy, smart waiting, and spec organization. Apply when writing or reviewing Cypress E2E tests.
cypress-excellence
Advanced Cypress testing patterns and best practices — custom commands, page objects, and network testing.
framework-architecture
Selenium + pytest framework architecture — configuration, fixtures, and dependency management.
testing
Android testing rules: fakes over mocks, ViewModel testing, Compose UI testing, Turbine, Truth.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.