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/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/mcp-intelligent-strategy)<a href="https://agentmods.dev/rules/mr-chen-05/rules-2.1-optimized-zh/mcp-intelligent-strategy"><img src="https://agentmods.dev/badge/rules/mr-chen-05/rules-2.1-optimized-zh/mcp-intelligent-strategy/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/mr-chen-05/rules-2.1-optimized-zh/mcp-intelligent-strategy"><img src="https://agentmods.dev/badge/rules/mr-chen-05/rules-2.1-optimized-zh/mcp-intelligent-strategy.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.01208 | $0.01208 |
| Opus 5 | $0.00604 | $0.00604 |
| Sonnet 5 | $0.00242 | $0.00242 |
| Haiku 4.5 | $0.00121 | $0.00121 |
Grade A, and why
mcp-intelligent-strategy 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 10d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨 MCP工具智能使用强制策略
⚠️ 重要：这是强制性规则，所有AI实例必须遵循！
🎯 核心强制原则
1. 任务开始时必须执行的检查
每个任务开始时，AI必须：
1. 立即扫描所有可用的MCP工具
2. 识别任务类型和复杂度
3. 评估MCP工具vs通用方法的效率
4. 选择最优方案执行
2. 强制性工具优先级
优先级排序（必须按此顺序考虑）：
1. 专用MCP工具（如github、memory、codebase-retrieval）
2. 通用MCP工具（如文件操作工具）
3. 通用方法（仅作为最后备选）
3. 强制性切换触发条件
以下情况必须重新评估工具选择：
- 通用方法连续失败2次以上
- 发现任务复杂度超出当前方法能力
- 识别到更优的MCP工具
- 用户反馈当前方法效率低下
4. 缺失工具的强制处理
当识别到需要但缺失的MCP工具时，必须：
1. 明确告知用户缺少的工具
2. 说明工具的具体价值和效率提升
3. 提供详细的配置指导
4. 主动协助用户完成配置
📋 强制性工具映射表
| 任务类型 | 必须首选的MCP工具 | 禁止的低效方法 |
|---|---|---|
| 文件操作 | server-filesystem 或文件系统MCP工具 |
逐个手动操作 |
| GitHub操作 | server-github 或GitHub MCP工具 |
web-fetch抓取HTML |
| 代码检索 | codebase-retrieval 或代码检索MCP工具 |
盲目搜索文件 |
| 用户反馈 | mcp-feedback-enhanced 或反馈MCP工具 |
简单文本询问 |
| 记忆管理 | server-memory 或记忆MCP工具 |
临时变量存储 |
| 数据库操作 | server-postgres, server-mysql 等 |
手动SQL操作 |
🔄 强制性执行流程
任务接收 → [强制]扫描MCP工具 → [强制]效率评估 → [强制]选择最优方案 → 执行监控 → [强制]动态调整
🛠️ 具体执行指令
文件操作任务
IF 任务涉及文件读写 THEN
首选：server-filesystem 或已配置的文件系统MCP工具
检测：扫描可用的文件操作MCP工具（如 d-frontend-files, e-vue-projects 等）
禁止：直接使用通用文件操作
切换条件：MCP工具不可用或功能不足
GitHub相关任务
IF 任务涉及GitHub操作 THEN
首选：server-github 或已配置的GitHub MCP工具
检测：扫描可用的GitHub MCP工具（如 github 等）
禁止：使用web-fetch抓取GitHub页面
切换条件：需要的功能GitHub工具不支持
代码分析任务
IF 任务需要理解或搜索代码 THEN
首选：codebase-retrieval MCP工具
禁止：手动逐文件搜索
切换条件：代码库过大或工具不可用
用户交互任务
IF 任务需要用户反馈或确认 THEN
首选：mcp-feedback-enhanced MCP工具
禁止：简单的文本询问
切换条件：需要复杂交互或工具不可用
🚨 违规检测
禁止的低效行为
- ❌ 有MCP工具可用时使用通用方法
- ❌ 连续失败2次以上不切换工具
- ❌ 发现缺失有用工具时不告知用户
- ❌ 不主动评估工具效率
必须的高效行为
- ✅ 任务开始时立即扫描MCP工具
- ✅ 优先选择最适合的MCP工具
- ✅ 遇到问题时主动重新评估工具选择
- ✅ 主动建议配置缺失的有用工具
📊 效果验证
自检清单
每个任务完成后，AI必须自问：
- 我是否在任务开始时扫描了MCP工具？
- 我是否选择了最优的工具方案？
- 我是否在遇到问题时重新评估了工具选择？
- 我是否主动建议了有用的缺失工具？
用户反馈指标
- 任务完成效率是否明显提升？
- 错误率是否显著降低？
- 用户是否感受到AI的智能化提升？
🎯 记住：这不是建议，而是必须严格遵循的强制性策略！
🚀 目标：让每个使用这个项目的AI都成为高效的MCP工具使用专家！
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.
- 10d ago First seen · 134 lines · 1,208 tokens per session scan A 624a4abd4a52
mcp-intelligent-strategy 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 1,208 tokens to every session, about $0.0060 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.