tech-stack

A set of backend technology rules for Node.js and Express.js, using MongoDB with Mongoose for data storage. It also specifies JWT authentication, Git, and possible Docker deployment.

In plain words
What is it for?
Use it when building an Express API, modeling MongoDB data with Mongoose, adding JSON Web Token login, or preparing deployment with Docker.
Why use it?
It gives a project a defined server, database, authentication, and version-control stack. This reduces uncertainty when starting or extending a backend.

Cursor rule

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/holtwood/awesome-cursorrules-zh/tech-stack
Clone the repo
git clone --depth 1 https://github.com/holtwood/awesome-cursorrules-zh
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 86 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found 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 $0.00000 $0.00086
Opus 5 $0.00000 $0.00043
Sonnet 5 $0.00000 $0.00017
Haiku 4.5 $0.00000 $0.00009

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

Security

Grade A, and why

tech-stack 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.

docs/rules/backend/nodejs/express-mongodb/tech-stack.mdc · 10 lines

What it actually says

  • 使用 Node.js 和 Express.js 作为后端。
  • 使用 MongoDB 和 Mongoose ODM 作为数据库。
  • 使用 JSON Web Tokens (JWT) 进行认证。
  • 考虑使用 Docker 进行部署。
  • 使用 Git 进行版本控制。
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 · 10 lines · 86 tokens per session scan A d87ed0c72264

Subscribe to this mod's changes

tech-stack is a cursor rule published in the GitHub repository holtwood/awesome-cursorrules-zh (231 stars, last pushed 27d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 86 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.