cursor-rules-template

A set of project rules for code structure, naming, errors, logging, files, tests, documentation, and pull requests. The rules organise code into layers such as data access, services, runtime, and user interface.

In plain words
What is it for?
Use it to guide coding work in a project that follows layered architecture, shared utilities, structured logs, common errors, external configuration, and required CI checks.
Why use it?
It gives an AI coding agent and human developers shared boundaries for making changes. This reduces inconsistent architecture, hidden dependencies, unvalidated data handling, and changes that skip tests or documentation.

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/wanfengzzz/harness-engineering/cursor-rules-template
Clone the repo
git clone --depth 1 https://github.com/WanfengzzZ/harness-engineering
Per session 282 This file is loaded in full into every session.
When invoked 282 The same file — it is already loaded in full.
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.00282 $0.00282
Opus 5 $0.00141 $0.00141
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

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

Security

Grade A, and why

cursor-rules-template 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.

assets/cursor-rules-template.mdc · 40 lines

What it actually says

项目规则

架构约束

  • 代码分层:Types → Config → Repo → Service → Runtime → UI
  • 横切关注点通过 Providers 注入
  • 禁止反向依赖(如 Service 不能引用 UI 组件)

编码规范

  • 优先使用 @/utils/ 下的共享工具包
  • 禁止 YOLO 式数据探测,必须验证边界
  • 日志使用结构化 logger,禁止 console.log
  • 错误处理使用统一的 AppError 类型
  • 配置外部化,禁止硬编码

文件规范

  • 单文件不超过 300 行
  • 单函数不超过 50 行
  • 命名遵循项目统一约定

提交规范

  • 代码变更必须包含测试
  • 文档必须与代码同步更新
  • PR 必须通过所有 CI 检查

文档导航

  • 架构文档:docs/design-docs/
  • 产品规格:docs/product-specs/
  • 黄金原则:docs/references/golden-principles.md
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 · 40 lines · 282 tokens per session scan A 3e683b2dbf33

Subscribe to this mod's changes

cursor-rules-template is a cursor rule published in the GitHub repository WanfengzzZ/harness-engineering (2 stars, last pushed 5mo ago), licensed MIT. It adds 282 tokens to every session, about $0.0014 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-31.