memforge-project-docs

Project rules saying that docs/ is the only place for documentation, with subfolders for areas such as architecture, APIs, analysis and feature work.

In plain words
What is it for?
Use them when finding, creating or relocating project documents, and when handling files formerly stored under .cursor/prDocs/.
Why use it?
They keep documentation in the directory used by Memforge's indexing tools and prevent documents from being scattered in obsolete locations.

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/zql0805/memforge/memforge-project-docs
Clone the repo
git clone --depth 1 https://github.com/zql0805/memforge
Per session 320 This file is loaded in full into every session.
When invoked 320 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.00320 $0.00320
Opus 5 $0.00160 $0.00160
Sonnet 5 $0.00064 $0.00064
Haiku 4.5 $0.00032 $0.00032

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

Security

Grade A, and why

memforge-project-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.

packages/memory-service/src/rules-templates/memforge-project-docs.mdc · 29 lines

What it actually says

项目文档管理规则

docs/ 目录

项目根目录下的 docs/ 目录为项目文档的唯一存放位置。 Memforge 的文档索引工具(index_documents / sync_documents / watch_docs)默认扫描此目录。

查找文档

  • 需要查阅项目文档时,在 docs/ 目录及其子目录中查找。

新增文档

  • 需要新建文档时,放入 docs/ 对应子目录:
    • docs/arch/ — 架构与设计文档
    • docs/api/ — 接口文档
    • docs/analysis/ — 分析报告
    • docs/code-review/ — Code Review 记录
    • docs/feature/ — 功能需求与重构指南
  • 如果对应子目录不存在,按需创建。

禁止使用 .cursor/prDocs/

  • 不再.cursor/prDocs/ 目录下创建或存放文档。
  • 如果发现项目中仍有 .cursor/prDocs/ 目录,应将其内容迁移到 docs/ 对应子目录后删除。
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 · 29 lines · 320 tokens per session scan A 87d97a47fed3

Subscribe to this mod's changes

memforge-project-docs is a cursor rule published in the GitHub repository zql0805/memforge (2 stars, last pushed 2mo ago), licensed MIT. It adds 320 tokens to every session, about $0.0016 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.