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/implement-taskgit clone --depth 1 https://github.com/Mr-chen-05/rules-2.1-optimized-zhWhat 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.00000 | $0.01433 |
| Opus 5 | $0.00000 | $0.00717 |
| Sonnet 5 | $0.00000 | $0.00287 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
implement-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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🎯 Task Implementation - 任务实现
系统化的任务实现方法，确保高质量交付。
🚀 Commands - 命令
/implement-task- 开始任务实现/task-plan- 制定实现计划/task-review- 任务审查/task-complete- 完成任务
📋 Process - 实现流程
1. 📊 任务分析 (Task Analysis)
- 理解任务需求和目标
- 分析技术要求和约束
- 识别依赖和风险
- 转换条件：需求清晰，方案可行
2. 📝 实现规划 (Implementation Planning)
- 制定详细实现计划
- 分解子任务和里程碑
- 分配资源和时间
- 转换条件：计划完整，可执行
3. 🔨 代码实现 (Code Implementation)
- 按计划实现功能
- 遵循代码规范
- 编写测试用例
- 转换条件：功能完成，测试通过
4. ✅ 质量保证 (Quality Assurance)
- 代码审查和重构
- 性能优化
- 文档更新
- 转换条件：质量达标，文档完整
5. 🚀 交付部署 (Delivery & Deployment)
- 集成测试
- 部署到环境
- 用户验收
- 转换条件：验收通过，部署成功
🛠️ Implementation Strategy - 实现策略
分解原则
- 垂直切分 - 按功能模块分解
- 水平切分 - 按技术层次分解
- 优先级排序 - 核心功能优先
- 依赖管理 - 合理安排依赖顺序
开发模式
- TDD - 测试驱动开发
- BDD - 行为驱动开发
- DDD - 领域驱动设计
- 敏捷开发 - 迭代增量
质量控制
- 代码审查 - Peer Review
- 自动化测试 - 单元/集成测试
- 静态分析 - 代码质量检查
- 性能监控 - 运行时监控
📋 Task Template - 任务模板
任务实现计划
## 任务概述
**任务名称**：[任务名称]
**优先级**：高/中/低
**预估工期**：X天
**负责人**：[姓名]
## 需求分析
### 功能需求
- [ ] 需求1：描述
- [ ] 需求2：描述
### 非功能需求
- [ ] 性能要求
- [ ] 安全要求
- [ ] 可用性要求
## 技术方案
### 架构设计
- 系统架构图
- 模块划分
- 接口设计
### 技术选型
- 框架/库选择
- 工具链配置
- 环境要求
## 实现计划
### 里程碑
1. [ ] 里程碑1 (Day 1-2)
2. [ ] 里程碑2 (Day 3-4)
3. [ ] 里程碑3 (Day 5-6)
### 风险识别
- 风险1：描述 + 缓解方案
- 风险2：描述 + 缓解方案
## 验收标准
### 功能验收
- [ ] 功能1测试通过
- [ ] 功能2测试通过
### 质量验收
- [ ] 代码覆盖率 > 80%
- [ ] 性能指标达标
- [ ] 安全扫描通过
✅ Best Practices - 最佳实践
实现原则
- 小步快跑 - 频繁提交和集成
- 持续反馈 - 及时沟通和调整
- 质量优先 - 不妥协代码质量
- 文档同步 - 代码和文档同步更新
协作方式
- 每日站会 - 同步进展和问题
- 代码审查 - 知识分享和质量保证
- 结对编程 - 复杂问题协作解决
- 技术分享 - 经验总结和传播
工具使用
- 版本控制 - Git工作流
- 项目管理 - 看板和燃尽图
- 自动化 - CI/CD流水线
- 监控告警 - 运行时监控
🔧 Tools Integration - 工具集成
开发工具
# 代码生成
npm run generate:component
npm run generate:api
# 代码检查
npm run lint
npm run type-check
# 测试运行
npm run test
npm run test:coverage
# 构建部署
npm run build
npm run deploy
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 · 207 lines · 0 tokens per session scan A 8643d602ca81
implement-task 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 costs nothing until one of its globs matches a file; then it loads 1,433 tokens. 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.
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.