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/Yoruto/prd-kitWrote 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/yoruto/prd-kit/00-workflow)<a href="https://agentmods.dev/rules/yoruto/prd-kit/00-workflow"><img src="https://agentmods.dev/badge/rules/yoruto/prd-kit/00-workflow/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/yoruto/prd-kit/00-workflow"><img src="https://agentmods.dev/badge/rules/yoruto/prd-kit/00-workflow.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.00762 | $0.00762 |
| Opus 5.5 | $0.00305 | $0.00305 |
| Sonnet 5.5 | $0.00152 | $0.00152 |
| Haiku 4.5 | $0.00076 | $0.00076 |
Grade A, and why
00-workflow 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.
What it actually says
项目协作主流程
四阶段模型
┌─────────────┐ ┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ 1. 设计阶段 │ → │ 2. 规划阶段 │ → │ 3. 实现阶段 │ → │ 4. 测试阶段 │
│ 10-design │ │ 15-planning │ │ 20-impl │ │ 30-testing │
└─────────────┘ └─────────────┘ └─────────────┘ └─────────────┘
↓ ↓ ↓ ↓
设计/PRD 实施计划 代码产出 测试通过
各阶段核心产出
| 阶段 | 核心产出 | 负责人角色 |
|---|---|---|
| 设计 | 设计文档 + PRD | 产品经理 |
| 规划 | 实施计划（任务拆解 + 依赖排序） | 架构师 |
| 实现 | 代码 + 单元测试 | 开发工程师 |
| 测试 | 测试报告 + 发布包 | QA / 开发 |
阶段准入准出
| 阶段 | 准入条件 | 准出标准 | 状态标记 |
|---|---|---|---|
| 设计 | 项目启动 | 设计评审通过 | design: stable |
| 规划 | PRD active | 实施计划确认 | plan: ready |
| 实现 | plan: ready | 代码完成 + 自测通过 | impl: done |
| 测试 | impl: done | 所有测试通过 | test: passed |
阶段衔接检查点
- 设计 → 规划：确认 PRD 状态为
active，技术方案清晰 - 规划 → 实现：确认实施计划
plan: ready，关键路径已识别 - 实现 → 测试：确认代码已提交，单元测试已编写
各阶段详细规则
| 阶段 | 规则文件 | 触发条件 | 角色 |
|---|---|---|---|
| 设计 | 10-design.mdc |
docs/design/**/*.md, docs/prd/**/*.md |
产品经理 |
| 规划 | 15-planning.mdc |
docs/plan/**/*.md, docs/prd/active/**/*.md |
架构师 |
| 实现 | 20-implementation.mdc |
代码文件, alwaysApply |
开发工程师 |
| 测试 | 30-testing.mdc |
**/*.test.*, **/*.spec.*, tests/** |
QA |
阶段角色说明
- 产品经理（10-design）：关注用户需求、产品价值、功能范围
- 架构师（15-planning）：关注系统拆解、依赖关系、技术风险、实施顺序
- 开发工程师（20-implementation）：关注代码质量、功能实现、单元测试
- QA（30-testing）：关注测试覆盖、缺陷发现、发布质量
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 First seen · 58 lines · 762 tokens per session scan A 29984a8cb77d
00-workflow is a cursor rule published in the GitHub repository Yoruto/prd-kit (1 stars, last pushed 28d ago), licensed MIT. It adds 762 tokens to every session, about $0.0030 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-31.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.
no-family-vocabulary-in-framework
The framework domain (packages/1-framework) carries no family- or target-specific vocabulary — types, fields, hooks, or strategy values — and, outside the CLI and the PSL parser's grammar names, no Prisma version name before 8. Enforced by the no-family-vocabulary Biome plugin plus the lint:ratchets ratchet.