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/renvia-code/best-cursor-rules/nodejsgit clone --depth 1 https://github.com/Renvia-code/best-cursor-rulesWhat 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 | $0.00000 | $0.02224 |
| Opus 5 | $0.00000 | $0.01112 |
| Sonnet 5 | $0.00000 | $0.00445 |
| Haiku 4.5 | $0.00000 | $0.00222 |
Grade A, and why
nodejs 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 yesterday.
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 — 439 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Node.js Backend Best Practices
Overview
| Aspect | Recommendation |
|---|---|
| Runtime | Node.js 20+ LTS |
| Framework | Express or Fastify |
| Language | TypeScript |
| Validation | Zod |
| ORM | Prisma or Drizzle |
Project Structure
src/
├── index.ts # Entry point
├── app.ts # Express app setup
├── config/
│ └── index.ts # Configuration
├── routes/
│ ├── index.ts # Route aggregator
│ └── users.ts # User routes
├── controllers/
│ └── users.ts # Request handlers
├── services/
│ └── users.ts # Business logic
├── middleware/
│ ├── auth.ts
│ └── errorHandler.ts
├── utils/
│ └── errors.ts
└── types/
└── index.ts
Express Setup
Application
// src/app.ts
import express from 'express'
import cors from 'cors'
import helmet from 'helmet'
import { errorHandler } from './middleware/errorHandler'
import routes from './routes'
const app = express()
// Security middleware
app.use(helmet())
app.use(cors({ origin: process.env.CORS_ORIGIN }))
// Body parsing
app.use(express.json())
app.use(express.urlencoded({ extended: true }))
// Routes
app.use('/api', routes)
// Error handling (must be last)
app.use(errorHandler)
export default app
Entry Point
// src/index.ts
import app from './app'
import { config } from './config'
const server = app.listen(config.port, () => {
console.log(`Server running on port ${config.port}`)
})
// Graceful shutdown
process.on('SIGTERM', () => {
console.log('SIGTERM received, shutting down gracefully')
server.close(() => {
console.log('Server closed')
process.exit(0)
})
})
Routes and Controllers
Route Definition
// src/routes/users.ts
import { Router } from 'express'
import { UserController } from '../controllers/users'
import { authenticate } from '../middleware/auth'
import { validate } from '../middleware/validate'
import { createUserSchema, updateUserSchema } from '../schemas/user'
const router = Router()
const controller = new UserController()
router.get('/', controller.getAll)
router.get('/:id', controller.getById)
router.post('/', validate(createUserSchema), controller.create)
router.patch('/:id', authenticate, validate(updateUserSchema), controller.update)
router.delete('/:id', authenticate, controller.delete)
export default router
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.
- yesterday First seen · 439 lines · 0 tokens per session scan A f4fa0c6d3b35
nodejs is a cursor rule published in the GitHub repository Renvia-code/best-cursor-rules (12 stars, last pushed 9mo ago), licensed CC0-1.0. It costs nothing until one of its globs matches a file; then it loads 2,224 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
cursor-tools-mastery
Cursor 3.7 runtime guide: choose the right tool, canvases, Design Mode, /worktree, /best-of-n, Await, and parallel execution where safe.
cursor-mcp-optimization
Cursor 3.7 MCP optimization: browser Design Mode, canvases, Figma, Cloudflare tools, MCP Apps structured content, and direct action patterns.
minimax-m3-verification
Extended M3 verification playbook: proof selection, multimodal-grounded checks, shell checks, browser checks, and recovery loops.
tool-discovery
MiniMax M3 + Cursor 3.7 tool discovery: runtime inventory, canvases, Design Mode inputs, schema-first MCP use, MCP Apps structured content, capability mapping, and safe fallbacks.
upload-report
Run automation and upload or verify Katalon Platform reports for Katalon Studio/KRE, JUnit XML, and Playwright reports. Use when you need to combine Katalon MCP project/result discovery with Katalon CLI execution, Katalon Report Uploader, or @katalon/playwright-reporter; configure report folders, report types…
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…