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/mr-chen-05/rules-2.1-optimized-zh/feedback-enhancedgit clone --depth 1 https://github.com/Mr-chen-05/rules-2.1-optimized-zhWrote 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/mr-chen-05/rules-2.1-optimized-zh/feedback-enhanced)<a href="https://agentmods.dev/rules/mr-chen-05/rules-2.1-optimized-zh/feedback-enhanced"><img src="https://agentmods.dev/badge/rules/mr-chen-05/rules-2.1-optimized-zh/feedback-enhanced.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.1 | $0.02216 | $0.02216 |
| Opus 5 | $0.01108 | $0.01108 |
| Sonnet 5 | $0.00443 | $0.00443 |
| Haiku 4.5 | $0.00222 | $0.00222 |
Grade A, and why
feedback-enhanced 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 5d 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 — 315 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🤖 Enhanced Feedback Mechanism - 增强反馈机制
专为复杂开发任务设计的智能反馈系统，支持1小时超时的深度交互。
🚀 Commands - 命令
/feedback- 手动触发反馈/feedback-config- 配置反馈设置/feedback-history- 查看反馈历史/feedback-summary- 生成工作摘要
✨ Features - 功能特性
🕐 Extended Timeout - 扩展超时
- 1小时超时 - 充足时间进行复杂架构讨论
- 自动保存 - 防止长时间讨论中的数据丢失
- 断点续传 - 支持中断后继续讨论
📝 Rich Text Support - 富文本支持
- 代码片段 - 语法高亮的代码展示
- 架构图 - Mermaid图表支持
- 配置文件 - 格式化的配置展示
- 截图支持 - 图片和截图集成
🔄 Real-time Interaction - 实时交互
- 双向沟通 - AI与用户的实时对话
- 进度跟踪 - 任务进度实时更新
- 决策记录 - 重要决策自动记录
📋 Trigger Conditions - 触发条件
自动触发场景
🔍 需求不明确
触发条件: 用户描述模糊或存在歧义
示例: "帮我做个网站" (缺少具体需求)
反馈内容:
- 项目类型和规模
- 技术栈偏好
- 功能需求清单
- 时间和预算约束
🎯 重大决策
触发条件: 架构选择、技术栈选型等关键决策
示例: 微服务 vs 单体架构选择
反馈内容:
- 项目规模和团队大小
- 性能和扩展性要求
- 运维能力和经验
- 长期维护考虑
✅ 方案完成
触发条件: 技术方案设计完成，需用户确认
示例: 数据库设计方案完成
反馈内容:
- 表结构设计审查
- 索引策略确认
- 性能预期评估
- 扩展性考虑
🎉 执行完成
触发条件: 代码实现完成，需用户验收
示例: API接口开发完成
反馈内容:
- 功能测试结果
- 性能指标达成
- 安全检查通过
- 文档完整性
🚨 错误发生
触发条件: 遇到无法自动解决的问题
示例: 依赖冲突或环境问题
反馈内容:
- 错误详细信息
- 可能的解决方案
- 需要的用户操作
- 替代方案建议
🎯 Specialized Feedback Scenarios - 专业反馈场景
🏗️ 架构设计确认
## 系统架构方案确认
### 当前方案
- **架构模式**: 微服务架构
- **技术栈**: Spring Boot + Docker + Kubernetes
- **数据库**: PostgreSQL + Redis
- **消息队列**: RabbitMQ
### 需要确认的要点
1. **服务拆分粒度** - 是否合理？
2. **数据一致性** - 如何处理分布式事务？
3. **服务通信** - REST vs gRPC选择？
4. **监控策略** - 日志和指标收集方案？
### 请提供反馈
- 团队规模和技术水平
- 预期并发量和数据量
- 运维能力和基础设施
- 项目时间线和里程碑
⚡ API设计确认
## API接口设计完成
### 接口概览
- **用户管理**: 15个接口
- **认证授权**: 8个接口
- **数据操作**: 23个接口
- **文件处理**: 6个接口
### 设计特点
- RESTful风格，统一响应格式
- JWT认证 + RBAC权限控制
- 请求限流和参数验证
- 完整的错误处理机制
### 需要确认
1. **接口粒度** - 是否符合业务需求？
2. **权限设计** - 角色和权限划分是否合理？
3. **性能考虑** - 是否需要缓存和优化？
4. **版本管理** - API版本策略是否合适？
🗄️ 数据库设计确认
## 数据库表结构设计
### 核心表设计
- **users**: 用户基础信息 (12字段)
- **roles**: 角色权限管理 (8字段)
- **products**: 产品信息 (15字段)
- **orders**: 订单数据 (18字段)
### 关系设计
- 用户-角色: 多对多关系
- 产品-分类: 一对多关系
- 订单-产品: 多对多关系
### 索引策略
- 主键索引: 所有表
- 唯一索引: email, phone
- 复合索引: (user_id, created_at)
- 全文索引: product_name, description
### 需要确认
1. **数据类型** - 字段类型选择是否合适？
2. **索引设计** - 查询性能是否满足要求？
3. **扩展性** - 是否考虑了未来的数据增长？
4. **备份策略** - 数据备份和恢复方案？
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.
- 5d ago First seen · 315 lines · 2,216 tokens per session scan A 99ae474f31b2
feedback-enhanced is a cursor rule published in the GitHub repository Mr-chen-05/rules-2.1-optimized-zh (29 stars, last pushed 1y ago), licensed MIT. It adds 2,216 tokens to every session, about $0.0111 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
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.
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.