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/ask-on-uncertainty)<a href="https://agentmods.dev/rules/yoruto/prd-kit/ask-on-uncertainty"><img src="https://agentmods.dev/badge/rules/yoruto/prd-kit/ask-on-uncertainty/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/ask-on-uncertainty"><img src="https://agentmods.dev/badge/rules/yoruto/prd-kit/ask-on-uncertainty.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.00616 | $0.00616 |
| Opus 5.5 | $0.00246 | $0.00246 |
| Sonnet 5.5 | $0.00123 | $0.00123 |
| Haiku 4.5 | $0.00062 | $0.00062 |
Grade A, and why
ask-on-uncertainty 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
与 PRD / 用户指令 / 项目栈的优先级
- PRD 或用户已写清的需求、验收标准、路径与命名 → 直接按文档执行，不必为同一事反复确认。
- PRD 未覆盖的架构取舍、业务规则、数值、交互流 → 必须先问再写。
- 技术栈/框架/ API 细节 → 先查当前项目已启用的 Stack Profile（若存在）、本仓库内类似实现、官方文档；仍不确定再提问。
遇到不确定时必须提问
规则
在以下场景中，若 PRD 或 config/PROJECT.md 未说明 且存在任何不确定，须先暂停并询问用户，再实现。
需要提问的场景
-
架构与放置位置
- 不确定应放在哪一模块/目录/包
- 不确定用哪种设计模式或分层
- 不确定类型应继承/组合/注入关系
-
实现手段
- 不确定某 API/库 的用法、参数、线程或异步契约
- 不确定与 UI/引擎/平台的绑定方式
- 不确定事件/信号/消息命名与触发点
- 不确定持久化/序列化/数据格式
-
业务与产品
- 不确定与需求相关的规则、范围、流程、数值
- 不确定边界情况或回退行为
-
命名与结构
- 不确定新文件/类型/导出名
- 不确定复用现成文件还是新建
禁止的行为
- 不要猜测后默默写进代码
- 不要用「差不多」方案代替与产品的对齐
- 不要用
TODO: 再改代替当下的澄清
提问的方式
简洁、点明不确定处与可选项，例如：
不确定：（具体内容）
选项 A：…
选项 B：…
请确认采用哪一项（或提供其它约束）。
适用范围
适用于计划、设计、实现与重构。与 00-prd-kit.mdc 及项目 config/PROJECT.md 不冲突时，本文件优先于「脑补」式实现。
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 · 62 lines · 616 tokens per session scan A 4991eef41350
ask-on-uncertainty is a cursor rule published in the GitHub repository Yoruto/prd-kit (1 stars, last pushed 28d ago), licensed MIT. It adds 616 tokens to every session, about $0.0025 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.