openspec-docs

A set of writing rules for OpenSpec documents. OpenSpec is a format for describing planned software changes and their requirements.

In plain words
What is it for?
Use it when writing or archiving OpenSpec proposals, designs, tasks, and specifications.
Why use it?
It keeps these documents in consistent Chinese while preserving the headings that OpenSpec tools need.

Cursor rule for Cursor

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/ly1836/spring-ai-rag-demo/openspec-docs
Clone the repo
git clone --depth 1 https://github.com/ly1836/spring-ai-rag-demo

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 345 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.00345
Opus 5 $0.00000 $0.00172
Sonnet 5 $0.00000 $0.00069
Haiku 4.5 $0.00000 $0.00034

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

Security

Grade A, and why

openspec-docs 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.

.cursor/rules/openspec-docs.mdc · 16 lines

What it actually says

OpenSpec 文档规则

  • openspec/ 下的 proposal.mddesign.mdtasks.mdspec.md 正文默认使用中文。
  • OpenSpec 工具可能依赖固定结构关键字;如模板或同步工具要求保留 ## ADDED Requirements### Requirement:#### Scenario:## Purpose## Requirements 等结构标记时,可以保留这些英文结构词,但其后的标题、说明、场景内容应使用中文。
  • 若主 spec 由 change 下的 delta spec 同步而来,源 delta spec 也应优先写成中文,否则同步结果会延续源文档语言。
  • 编写 spec.md 时优先保证结构兼容性,其次保证语言一致性;不要为了翻译把 OpenSpec 所需层级或关键标记改坏。
  • spec 的标题也应优先使用中文,例如 # <capability> 规格,不要保留 CLI 自动生成的 # <capability> Specification 英文标题。
  • ## Purpose 段落必须写成正式中文说明,禁止保留 TBD - created by archiving change ...Update Purpose after archive. 等英文占位文案。
  • 当归档或同步主 spec 时,如果工具自动生成了英文外壳,必须在归档流程结束前立即改写为中文,再视为完成。
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. yesterday First seen · 16 lines · 0 tokens per session scan A dd0876cb7bc2

Subscribe to this mod's changes

openspec-docs is a cursor rule published in the GitHub repository ly1836/spring-ai-rag-demo (84 stars, last pushed 29d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 345 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.