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/xc404/kiwi/plans-in-workspacegit clone --depth 1 https://github.com/xc404/kiwiWrote 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/xc404/kiwi/plans-in-workspace)<a href="https://agentmods.dev/rules/xc404/kiwi/plans-in-workspace"><img src="https://agentmods.dev/badge/rules/xc404/kiwi/plans-in-workspace.svg" alt="Measured on agentmods" 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 | $0.00483 | $0.00483 |
| Opus 5 | $0.00242 | $0.00242 |
| Sonnet 5 | $0.00097 | $0.00097 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
plans-in-workspace 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 4d 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.
What it actually says
计划文件自动保存规则
强制行为
凡生成或修订 plan（实施计划、路线图、设计草案等结构化规划文档），必须在同一次回复中用 Write 工具写入磁盘，禁止仅在对话中输出而不落盘。
保存位置
- 路径：
<工作区根目录>/.cursor/plans/ - 命名：
<功能描述>_<8位短哈希>.plan.md（如frontend_intermediate_catch_event_82ba8a18.plan.md） - 短哈希：对功能描述或日期取稳定片段即可，保证同主题不重复覆盖已有文件
- 目录不存在时：写入前确保
.cursor/plans/存在（Write 失败则用 Shell 创建）
禁止的位置
- ❌ 用户主目录（
C:\Users\<用户名>\等） - ❌ 系统临时目录（
%TEMP%） - ❌ 其他工作区根目录
- ❌ Cursor 全局目录（
~/.cursor/，非<workspace>/.cursor/）
工作流
- 拟定 plan 内容
- 立即 Write 到
.cursor/plans/<name>.plan.md - 在回复中附上已保存文件的工作区相对路径（如
.cursor/plans/xxx.plan.md），便于打开 - 后续修订 plan 时，更新同一文件（或按主题新建带新哈希的文件），不要只改对话文本
多工作区
同时打开多个工作区时，将 plan 保存到主要涉及的那个工作区的 .cursor/plans/；跨工作区变更保存到改动最多的工作区。
与 OpenSpec 的关系
- OpenSpec change（
openspec/changes/）走规格驱动流程，与 plan 互补，不互相替代 - 用户未要求 OpenSpec 时，复杂任务仍应写 plan 并落盘
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.
- 4d ago First seen · 41 lines · 483 tokens per session scan A e94bfbfec889
plans-in-workspace is a cursor rule published in the GitHub repository xc404/kiwi (7 stars, last pushed 9d ago), licensed MIT. It adds 483 tokens to every session, about $0.0024 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.
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.