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/epam/ai-dial-chatWrote 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/epam/ai-dial-chat/nestjs-best-practices)<a href="https://agentmods.dev/rules/epam/ai-dial-chat/nestjs-best-practices"><img src="https://agentmods.dev/badge/rules/epam/ai-dial-chat/nestjs-best-practices.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.00014 | $0.00014 |
| Opus 5 | $0.00007 | $0.00007 |
| Sonnet 5 | $0.00003 | $0.00003 |
| Haiku 4.5 | $0.00001 | $0.00001 |
Grade A, and why
nestjs-best-practices 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 8d 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
../../.claude/rules/nestjs-best-practices.md
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.
- 8d ago First seen · 1 lines · 14 tokens per session scan A 516e7e3b7c9b
nestjs-best-practices is a cursor rule published in the GitHub repository epam/ai-dial-chat (504 stars, last pushed today), licensed Apache-2.0. It adds 14 tokens to every session, about $0.0001 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
tsoa-rules
This document outlines comprehensive guidelines and best practices for developing Node.js server-side applications with tsoa, focusing on TypeScript for type safety and OpenAPI specification generation.
pn-go-backend
Go backend style, env, and error handling. Use for API and server code (Gin, Fiber, Echo).
pn-php-backend
PHP backend style, env, and error handling. Use for API and server code (Laravel, Slim).
pn-python-backend
Python backend style, env/secrets, and error handling. Use for API and server code (FastAPI, Flask).
pn-ruby-backend
Ruby backend style, env, and error handling. Use for API and server code (Rails, Sinatra).
pn-rust-backend
Rust backend style, env, and error handling. Use for API and server code (Actix-web, Axum).