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/wangqiqi/cursor-ai-rulesWrote 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/wangqiqi/cursor-ai-rules/intelligent_evolution-strategies)<a href="https://agentmods.dev/rules/wangqiqi/cursor-ai-rules/intelligent_evolution-strategies"><img src="https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/intelligent_evolution-strategies.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.00000 | $0.00403 |
| Opus 5 | $0.00000 | $0.00201 |
| Sonnet 5 | $0.00000 | $0.00081 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
intelligent_evolution-strategies 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 8d 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
智能演进策略 (Strategies)
本规则由
@intelligent_evolution引用
意图分类体系
# 一级意图
creation: ["创建", "开发", "构建", "设计", "实现"]
optimization: ["优化", "改进", "重构", "升级"]
analysis: ["分析", "评估", "诊断", "检查"]
# 二级意图
frontend: ["前端", "界面", "UI", "React", "Vue"]
backend: ["后端", "API", "服务", "Node.js", "Python"]
ai_ml: ["AI", "机器学习", "训练", "推理"]
上下文引用策略
- 语义关联分析：基于对话内容分析相关文件
- 代码依赖追踪：识别相关联的模块
- 历史上下文记忆：记住对话和引用模式
- 相关性评分排序：为候选文件计算分数
模块同步触发条件
- 共享资源修改（常量、类型、配置）
- 接口变更（API、函数签名）
- 依赖关系变化
- 架构重构
同步影响分析
- 检测变更 → 2. 分析影响 → 3. 生成同步计划 → 4. 智能提醒 → 5. 用户确认执行 → 6. 学习优化
个性化学习维度
- 沟通偏好、编码风格
- 项目模式、任务效率
引用: @intelligent_evolution
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.
- 8d ago First seen · 52 lines · 0 tokens per session scan A 16c25033bb12
intelligent_evolution-strategies is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (16 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 403 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
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.