nodejs-mongodb-jwt-express-react-cursorrules-promp

nodejs-mongodb-jwt-express-react-cursorrules-promp is a cursor rule for Cursor from PatrickJS/awesome-cursorrules. It costs 443 tokens per session, scanned A, a copy of nodejs-mongodb-cursorrules-prompt-file-tutorial, CC0-1.0.

A set of project rules for a full-stack application using Node.js, Express, MongoDB, Mongoose, JSON Web Tokens, React, and optionally Docker. It describes how users submit paid requests, administrators approve them, and entries manage separate picks.

In plain words
What is it for?
Use it when developing the pool, payment, approval, entry, and pick features for this React and Node.js application.
Why use it?
It keeps backend and frontend changes aligned with the application's user flow and game rules, while encouraging secure APIs, validation, and planning before implementation.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: mentions Cursor.

About the project

PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.

PatrickJS/awesome-cursorrules · 40,732 stars · on GitHub

Install

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.

agentmods
npx agentmods add rules/patrickjs/awesome-cursorrules/nodejs-mongodb-jwt-express-react-cursorrules-promp
Clone the repo
git clone --depth 1 https://github.com/PatrickJS/awesome-cursorrules

Made for: Cursor.

Wrote 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.

agentmods badge for nodejs-mongodb-jwt-express-react-cursorrules-promp

README.md
[![agentmods](https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/nodejs-mongodb-jwt-express-react-cursorrules-promp.svg)](https://agentmods.dev/rules/patrickjs/awesome-cursorrules/nodejs-mongodb-jwt-express-react-cursorrules-promp)
Your own site
<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/nodejs-mongodb-jwt-express-react-cursorrules-promp"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/nodejs-mongodb-jwt-express-react-cursorrules-promp.svg" alt="Measured on agentmods" height="20"></a>
Per session 443 This file is loaded in full into every session.
When invoked 443 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00443 $0.00443
Opus 5 $0.00221 $0.00221
Sonnet 5 $0.00089 $0.00089
Haiku 4.5 $0.00044 $0.00044

Measured 2d ago against content hash 2e5619795c55, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

nodejs-mongodb-jwt-express-react-cursorrules-promp 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 2d 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.

Origin

This is a copy

97% identical to nodejs-mongodb-cursorrules-prompt-file-tutorial — 94 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

rules/nodejs-mongodb-jwt-express-react-cursorrules-promp.mdc · 73 lines

What it actually says

Tech Stack:

Backend: Node.js with Express.js
Database: MongoDB with Mongoose ODM
Frontend: React.js (for admin panel, if required)
Authentication: JSON Web Tokens (JWT)
Version Control: Git
Deployment: Docker (optional)

Precision in User Requirements:

Strictly adhere to specified user flow and game rules.

Strategy:

Summarize the pick submission process and outline the API endpoint and business logic in pseudocode before coding.

Strategic Planning with Pseudocode:

Begin each feature with detailed pseudocode.
Example: Provide pseudocode for the weekly scoring process, detailing steps from game result input to entry status updates.

Code Quality:

Ensure secure, efficient code following RESTful API best practices.
Implement proper error handling and input validation.

User Flow:

Users browse available Pools
Submit up to 3 Requests per Pool
Complete payment for Requests
Admin approves/rejects Requests
Approved Requests become Entries

Entry Management:

Each user can have up to 3 Entries per Pool
Entries are numbered 1, 2, 3
Picks are made and tracked separately for each Entry

Pick Management:

Users make Picks for each Entry separately
Picks can be updated until deadline (game start or 1PM Sunday of the current week of the pick)

Scoring and Ranking:

Picks scored after games complete
Win: Entry moves to next week
Loss: Entry eliminated from Pool
Each Entry ranked separately in Pool standings

Results and Standings:

Users view Picks/scores for each Entry separately
Pool standings show all Entries (multiple per User possible)
Pool members can view all Picks after scoring

Key Implementation Points:

Limit Requests to 3 per User per Pool
Track Requests and Entries separately (numbered 1, 2, 3)
Implement payment status tracking in Request model
Create Entry only after admin approval and payment completion
Admin interface for managing and approving Requests
Implement state transitions (Request: pending -> approved -> Entry created)

Changes

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.

  1. 2d ago First seen · 73 lines · 443 tokens per session scan A 2e5619795c55

Subscribe to this mod's changes

nodejs-mongodb-jwt-express-react-cursorrules-promp is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,732 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 443 tokens to every session, about $0.0022 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to nodejs-mongodb-cursorrules-prompt-file-tutorial, differing in 94 lines, and is treated as a copy.