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/GoranErhartic/cursor-development-rulesWrote 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/goranerhartic/cursor-development-rules/nodejs-base)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/nodejs-base"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/nodejs-base/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/rules/goranerhartic/cursor-development-rules/nodejs-base"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/nodejs-base.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.00000 | $0.00858 |
| Opus 5.5 | $0.00000 | $0.00343 |
| Sonnet 5.5 | $0.00000 | $0.00172 |
| Haiku 4.5 | $0.00000 | $0.00086 |
Grade A, and why
nodejs-base 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js + TypeScript Base Development Guide
Stack
| Layer | Technology |
|---|---|
| Runtime | Node.js (LTS) |
| Language | TypeScript |
| Frameworks | Express, Fastify, NestJS, Hono |
| Validation | Zod |
| Data | Prisma, Drizzle, TypeORM |
| Logging | Pino, Winston |
| Testing | Vitest, Supertest, Testcontainers |
| Package Manager | pnpm preferred |
Rule Routing
Consult these rules based on what you are working on:
Quick Reference
- Add/modify API endpoint:
languages/nodejs/controllers.mdc,languages/nodejs/validation.mdc,languages/nodejs/error-handling.mdc - Add persistence logic:
languages/nodejs/orm.mdc,languages/nodejs/testing.mdc - Improve reliability:
languages/nodejs/resilience.mdc,languages/nodejs/logging.mdc,languages/nodejs/security.mdc - Integrate third-party calls:
languages/nodejs/http-clients.mdc,languages/nodejs/error-handling.mdc
API & Controllers
- Controller patterns (Express, Fastify, NestJS, Hono) →
languages/nodejs/controllers.mdc - Request validation (Zod schemas, type inference) →
languages/nodejs/validation.mdc - Input sanitization (XSS, SQL injection, path traversal) →
languages/nodejs/input-sanitization.mdc
Data & Persistence
- ORM patterns (Prisma, Drizzle, TypeORM, migrations) →
languages/nodejs/orm.mdc
Cross-Cutting
- Code quality (ESLint, Prettier, TypeScript, naming) →
languages/nodejs/code-quality.mdc - Error handling (Result pattern, middleware, ProblemDetail RFC 7807) →
languages/nodejs/error-handling.mdc - Logging (Pino, Winston, correlation IDs) →
languages/nodejs/logging.mdc - Security (Helmet, CORS, rate limiting, OWASP) →
languages/nodejs/security.mdc - Auth (JWT, Passport, RBAC) →
languages/nodejs/auth.mdc - HTTP clients (fetch, axios, undici, resilience) →
languages/nodejs/http-clients.mdc - Resilience (retry, circuit breaker, timeout, bulkhead) →
languages/nodejs/resilience.mdc - Messaging (BullMQ, job queues, event-driven) →
languages/nodejs/messaging.mdc - Testing (Vitest, Supertest, Testcontainers, mocking) →
languages/nodejs/testing.mdc - Dependencies (package.json, security, licensing) →
languages/nodejs/dependencies.mdc
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.
- 1mo ago First seen · 67 lines · 0 tokens per session scan A 9afec8bf4c84
nodejs-base is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 858 tokens. 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
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
typescript-patterns
Cursor rule "typescript-patterns" from fmflurry/settings-opencode, covering typescript/javascript patterns, api response format, custom hooks pattern and repository pattern.
standard-nestjs-module-hierarchy
Establish a consistent NestJS module structure in the API application where each resource is encapsulated in its own module with proper hierarchical organization to enhance maintainability, scalabilit... .
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
nestjs
This guide provides opinionated, actionable best practices for building robust, scalable, and maintainable NestJS applications using TypeScript, emphasizing modern patterns and common pitfalls.