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.
git clone --depth 1 https://github.com/double-coding-lab/Flow2SpecWrote 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.
[](https://agentmods.dev/rules/double-coding-lab/flow2spec/f2s-topic-authoring)<a href="https://agentmods.dev/rules/double-coding-lab/flow2spec/f2s-topic-authoring"><img src="https://agentmods.dev/badge/rules/double-coding-lab/flow2spec/f2s-topic-authoring/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/double-coding-lab/flow2spec/f2s-topic-authoring"><img src="https://agentmods.dev/badge/rules/double-coding-lab/flow2spec/f2s-topic-authoring.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.04633 |
| Opus 5.5 | $0.00016 | $0.01853 |
| Sonnet 5.5 | $0.00008 | $0.00927 |
| Haiku 4.5 | $0.00004 | $0.00463 |
Grade A, and why
f2s-topic-authoring 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Flow2Spec 主题创作准则（Topic Authoring）
本条为 创作侧 单一事实源；凡 f2s-* 技能在新增或修改 .Knowledge/topics/<topic>.md、调整 manifest-routing.topicMetadata / manifest-routing.topicDependencies、删除 / 迁移 topic 时，必须先 Read 本条全文，再按对应 SKILL 的步骤继续。与 f2s-flow2spec-unified-entry（消费侧）并存；硬冲突时以统一入口为准。
适用范围
满足下列任一即「触达本条」：
- 新增或重写
.Knowledge/topics/<topic>.md； - 修改既有 topic 的标题 / 适用场景 / 关键流程边界；
- 新增、删除或调整
manifest-routing.topicMetadata； - 在
manifest-routing.topicDependencies中新增、删除或调整依赖边； - 在
taskToTopicRules[].topics中新增引用某个 topic id； - 删除或迁移 topic（
f2s-kb-rm/f2s-kb-upgrade）。
1. topic 命名
- id：
kebab-case，与manifest-routing.topicPaths的 key 一致。 - 业务命名：topic id、文件名、标题以及派生 matcher id 按职责命名，不拼接下游项目名、仓库名或
package.json.name前缀；项目身份放在正文。项目架构概览固定为project-architecture/project-architecture.md/项目架构，其源文档为项目架构终稿.md。既有f2s-*技能/规则同源标识保留。 - 文件名：
.Knowledge/topics/<topic-id>.md；若该 topic 与同名f2s-*技能 / 规则强绑定（如f2s-task/f2s-req-plan），文件名可加f2s-前缀以示同源。 - 不要：版本后缀（
-v2/-new）、个人花名、与index.md行级标题冲突的同义词。
2. topic 定位与正文骨架
本规则下文的 *_终稿.md 同时包含固定命名的 项目架构终稿.md；它是合法的终稿事实源，无需补下划线或项目名前缀。
topic 的定位：可执行路由摘要 + 关键边界。topic 可以包含必要的边界说明、关键流程步骤、禁止项、配置摘要——Agent 读完即可执行或判断是否需要继续下钻；不应承载完整实现细节、长文背景或可在 stock-doc 里查的原始内容。stock-doc 承载完整背景与长文细节，topic 指向它。
长文背景引用的目录边界（硬约束）：topic 中「详细背景 / 相关资料 / 长文来源 / 参考文档」等指向长文源的引用槽位，只允许指向 .Knowledge/stock-docs/*_终稿.md 或已被归档为长文事实的 stock-docs/*；禁止把这类槽位挂到 .Knowledge/req-docs/*（含澄清 / 技术方案 / SQL / PRD 等）——req-docs 是本次交付的临时输入，用完会随任务归档或迁移，作为 topic 的长文事实源是悬空引用。若同步 / 新建 topic 时相应 stock-docs/*_终稿.md 尚未生成，必须先触发 f2s-doc-final 沉淀终稿（或与用户确认由手写补齐），再让 topic 指向终稿；不得跳过终稿直接把 topic 挂在 req-docs 上。允许：topic 正文可短引方案里的一句结论或一个字段名作为佐证（如「见 .Knowledge/req-docs/xxx_技术方案.md」的偶发点引），但长文背景槽位（"详细背景 / 相关资料"整节）仍须指向 stock-doc。
每个 topic 至少包含：
- 标题与一句话意图（一行写清"该 topic 解决什么"）；
- 适用场景 / 触发词（与对应
matchers/<id>.jsonincludeAny/includeAll语义一致）； - 核心规则 / 流程（可执行知识；步骤须可由 Agent 复现）；
- 依赖声明（若
topicDependencies中存在依赖项，正文须显式写一句「执行前须先读依赖主题<dep>」，参考topics/f2s-req-plan.md首段写法）； - 边界与禁止项（避免膨胀到隔壁 topic）；
- 长文背景 / 详细资料引用（如需承载业务背景）：只列
.Knowledge/stock-docs/*_终稿.md的可点击 Markdown 链接（1–3 条即可）；禁止直接列.Knowledge/req-docs/*作为长文背景来源；无对应终稿时先生成终稿再回填此小节。
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.
- 1mo ago Changed · +4 lines c88d85889f04
- 1mo ago Changed · +36 lines f380b5a7dc0b
- 1mo ago First seen · 127 lines · 40 tokens per session scan A 879350a6e4a6
f2s-topic-authoring is a cursor rule published in the GitHub repository double-coding-lab/Flow2Spec (52 stars, last pushed 6d ago), licensed MIT. It adds 40 tokens to every session and 4,633 once invoked, about $0.0002 per session on Opus 5.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-30.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .