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.
npx agentmods add rules/double-coding-lab/flow2spec/f2s-taskgit clone --depth 1 https://github.com/double-coding-lab/Flow2SpecWhat 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 | $0.05259 | $0.05259 |
| Opus 5 | $0.02629 | $0.02629 |
| Sonnet 5 | $0.01052 | $0.01052 |
| Haiku 4.5 | $0.00526 | $0.00526 |
Grade A, and why
f2s-task 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.
How it starts
The opening of the file, as written. The whole thing — 308 lines — stays where its author put it; the contents beside it link to each section on GitHub.
f2s-task（变更追踪规则）
生效条件
各技能按自身子项判断：
f2s-kb-feat：读changeTracking.featf2s-kb-fix：读changeTracking.fixf2s-implement-tech-design：读changeTracking.implement
若对应子项为 false 或字段不存在，该技能内的变更追踪步骤不执行，直接跳过。
f2s-req-plan命令不受此条件约束，始终执行（见skills/f2s-req-plan/SKILL.md）。
多人协作与任务根 TASK_ROOT（必须先解析）
进入本规则任何「读/写 .task」步骤前，必须 Read("flow2spec.config.json")，并解析 TASK_ROOT（本会话内固定，禁止中途改 id）：
| 条件 | TASK_ROOT |
developerId 来源 |
|---|---|---|
collaboration.enabled === false |
.task |
legacy（强制单人根） |
collaboration.developerId 非空（trim 后） |
.task/<sanitize(id)> |
config |
否则能读到 git config user.email |
.task/<sanitize(email@前)> |
git-email |
否则能读到 git config user.name |
.task/<sanitize(name)> |
git-name |
| 仍无 | .task |
legacy（单人旧布局；须在回复中提示：建议配置 collaboration.developerId） |
sanitize：小写；若含 @ 只取本地部分；非 [a-z0-9] 收成 -；去首尾 -；长度 1–64，否则视为无 id。
路径一律用 TASK_ROOT 前缀（下面凡写 TASK_ROOT/... 均指解析结果）：
- 索引：
TASK_ROOT/todo.json - 进行中：
TASK_ROOT/active/<task-name>/ - 已完成：
TASK_ROOT/completed/<YYYYMMDD>-<task-name>/
防串戏（硬约束）：
- 只读写当前会话的
TASK_ROOT；禁止为续作/匹配去遍历.task/*/todo.json或其他 developer 目录。 - keywords 匹配范围 仅 当前
TASK_ROOT/todo.json内条目。 - 创建任务时
todo.json的folder必须写成当前TASK_ROOT/active/<task-name>/（posix 相对路径）。 - 可选在任务开始时向用户回显一行：
[task] developerId=<id|legacy> TASK_ROOT=<path>。 .Knowledge/仍为全员共享；本规则不按人拆分知识库。
实现参考（CLI/工具）：包内
lib/developerId.js的resolveDeveloperContext/taskRootFor（与上表同口径）。
f2s-req-plan 调用时的绑定
执行 f2s-req-plan（或续作命中 linkedSkill: "f2s-req-plan"）时：
- 不受
changeTracking.feat/fix/implement限制，但 必须 按本规则「任务开始 / 执行中 / 中断与会话结束 / 任务完成 / 新会话续作」维护TASK_ROOT下任务树； - 技能 步骤 0 须
Read本规则全文（Cursor/Claude：rules/f2s-task.*；Codex：.codex/topics/f2s-task.md）； - 落盘、打钩、归档、
user-todos.md/acceptance.md格式 以本规则为准；技能正文不得省略todo.json/user-todos.md/acceptance.md，不得改写归档目录命名（<YYYYMMDD>-<task-name>）。
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.
- 2d ago First seen · 308 lines · 5,259 tokens per session scan A 7757f5031874
f2s-task is a cursor rule published in the GitHub repository double-coding-lab/Flow2Spec (47 stars, last pushed 4d ago), licensed MIT. It adds 5,259 tokens to every session, about $0.0263 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-30.
Other cursor rules, from other repositories
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.