What is evolution-governance?

A governance rule set for changing other rules safely. Governance here means checking risks, testing changes, reviewing them, and monitoring the result.

Use it to assess proposed changes, define rollback and monitoring plans, validate rules, run tests, conduct reviews, and release changes gradually.

Unplanned rule changes can cause security, compatibility, or user-impact problems. These rules require a rollback plan, testing, staged rollout, and follow-up monitoring.

evolution-governance — Cursor rule for Cursor by wangqiqi: A governance rule set for changing other rules safely.

Install

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.

agentmods

npx agentmods add rules/wangqiqi/cursor-ai-rules/evolution-governance

Clone the repo

git clone --depth 1 https://github.com/wangqiqi/cursor-ai-rules

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,699 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00000	$0.01699
Opus 5	$0.00000	$0.00849
Sonnet 5	$0.00000	$0.00340
Haiku 4.5	$0.00000	$0.00170

Measured 3d ago against content hash 7ba1f8208489, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

evolution-governance 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 3d 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.

.cursor/rules/evolution/evolution-governance.mdc · 233 lines

How it starts

The opening of the file, as written. The whole thing — 233 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🛡️ 演进治理机制 (Evolution Governance)

版本: v4.3.0 | 最后更新: {{GENERATION_TIME}} | 作者: wangqiqi (https://github.com/wangqiqi)

🎯 治理原则 (Governance Principles)

演进治理基于 @evolution-philosophy 的核心原则，专注于规则演进过程的安全保障和质量控制。

核心定位：作为演进过程的守门人和质量把关者，确保所有演进活动符合哲学原则并满足安全要求。

⚠️ 治理执行原则

MUST 遵循以下治理原则：

NEVER 在没有回滚计划的情况下进行变更
MUST 在变更前完成风险评估
ALWAYS 先在测试环境验证
MUST 监控变更后的系统状态
DO NOT 跳过灰度发布阶段

🛡️ 安全保障机制 (Safety Safeguards)

风险控制 (Risk Control)

变更前评估 (Pre-Change Assessment)

评估清单：
- [ ] 影响范围分析：哪些用户/项目会受影响
- [ ] 回滚计划：如何快速恢复到之前状态
- [ ] 监控指标：如何检测问题和衡量成功
- [ ] 应急预案：出现问题时的处理流程

灰度发布 (Canary Deployment)

rollout_strategy:
  phases:
    - name: "pilot"
      scope: "10% of users"
      duration: "1 week"
      success_criteria: "no critical issues"
    - name: "beta"
      scope: "50% of users"
      duration: "2 weeks"
      success_criteria: "satisfaction > 80%"
    - name: "production"
      scope: "100% of users"
      monitoring: "continuous"

质量控制 (Quality Control)

自动化测试 (Automated Testing)

规则语法验证
功能正确性测试
性能影响评估
兼容性检查

人工审核 (Manual Review)

安全专家审核
用户体验评估
文档完整性检查
社区反馈收集

📊 监控与度量 (Monitoring & Metrics)

关键指标 (Key Metrics)

演进效率指标 (Evolution Efficiency)

{
  "evolution_efficiency": {
    "average_improvement_time": "2.3 days",
    "success_rate": "87%",
    "user_adoption_rate": "92%"
  }
}

系统稳定性指标 (System Stability)

{
  "system_stability": {
    "uptime_percentage": "99.8%",
    "error_rate": "0.02%",
    "rollback_frequency": "0.5 per month"
  }
}

用户满意度指标 (User Satisfaction)

{
  "user_satisfaction": {
    "nps_score": 8.5,
    "feature_usage_rate": "78%",
    "support_ticket_reduction": "35%"
  }
}

监控体系 (Monitoring System)

实时监控 (Real-time Monitoring)

规则执行状态
系统性能指标
用户反馈收集
异常情况告警

定期报告 (Periodic Reporting)

周度演进摘要
月度效果评估
季度趋势分析
年度回顾总结

🔄 版本管理 (Version Management)

语义化版本控制 (Semantic Versioning)

主版本.次版本.补丁版本
├── 主版本：重大架构调整或不兼容变更
├── 次版本：新功能添加或重要改进
└── 补丁版本：bug修复或小幅优化

Read the full file on GitHub · 233 lines

Changes

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.

3d ago First seen · 233 lines · 0 tokens per session scan A 7ba1f8208489

Subscribe to this mod's changes

evolution-governance is a cursor rule published in the GitHub repository wangqiqi/cursor-ai-rules (15 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,699 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.