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)<a href="https://agentmods.dev/rules/wangqiqi/cursor-ai-rules/intelligent_evolution"><img src="https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/intelligent_evolution/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/wangqiqi/cursor-ai-rules/intelligent_evolution"><img src="https://agentmods.dev/badge/rules/wangqiqi/cursor-ai-rules/intelligent_evolution.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.00000 | $0.00377 |
| Opus 5.5 | $0.00000 | $0.00151 |
| Sonnet 5.5 | $0.00000 | $0.00075 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
intelligent_evolution 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
🧠 智能演进系统 (Intelligent Evolution System)
版本: v4.4.0 | 已拆分入口与策略至独立规则
核心理念
智能演进系统专注于项目的智能化感知和分析，为演进决策提供数据支持。
系统定位：作为项目感知和分析的专门系统，为各种演进活动提供智能数据支持。
📚 详细规范引用
- 系统入口：见
@intelligent_evolution-entry（架构、感知能力表、感知模式、数据存储） - 演进策略：见
@intelligent_evolution-strategies（意图识别、上下文引用、模块同步、学习引擎）
核心能力
- 项目状态感知、用户行为分析、环境特征检测
- 对话意图感知、上下文感知引用
- 个性化学习引擎、模块同步感知
- 性能监控系统
📋 使用示例
# 触发智能演进分析
/master 优化项目规则
/master 分析项目并改进
/master 学习用户习惯后调整
# 或通过对话
"帮我看看规则系统有哪些可以优化的地方"
"根据最近的使用情况，有什么改进建议？"
引用: @intelligent_evolution-entry @intelligent_evolution-strategies
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 · 46 lines · 0 tokens per session scan A 3a951741ff42
intelligent_evolution is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (17 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 377 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.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.