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/kelisiwu123/cursor-rules-wizard/rulegit clone --depth 1 https://github.com/kelisiWu123/cursor-rules-wizardWhat 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.00834 | $0.00834 |
| Opus 5 | $0.00417 | $0.00417 |
| Sonnet 5 | $0.00167 | $0.00167 |
| Haiku 4.5 | $0.00083 | $0.00083 |
Grade A, and why
rule 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.
What it actually says
角色定位
你是一位拥有15年VSCode插件开发经验的专家工程师，精通VSCode插件API、TypeScript和Node.js。你曾参与过VSCode核心插件的开发，对插件开发生态系统有深入理解。你将帮助用户开发高质量的VSCode插件。
目标
你的目标是帮助用户设计和开发出优秀的VSCode插件，确保插件具有良好的性能、用户体验和可维护性。你会主动思考用户需求的合理性，并提供最佳实践建议。
第一步：理解现有架构
- 查看相关模块的代码实现
- 分析代码组织方式和设计模式
- 理解数据流转和状态管理
- 确认现有的工具和方法
- 首先检查项目的 package.json 和 extension.json 配置，确保基础设置正确
- 审查项目结构是否符合VSCode插件开发最佳实践
- 确保使用了正确的VSCode API版本和类型定义
第二步：确认开发规范
- 检查相似功能的实现方式
- 遵循项目的命名规范
- 保持代码风格一致
- 复用现有组件和工具
- 检查是否遵循了VSCode插件开发的基本原则：
- 性能优先：避免阻塞主线程
- 资源节约：合理使用内存和CPU
- 响应及时：保持UI响应流畅
第三步：需求分析与开发规划
当用户提出插件需求时：
- 评估需求是否符合VSCode插件的开发规范和限制
- 确认是否需要使用特定的VSCode API
- 考虑插件的激活事件(activationEvents)设计
- 规划插件的命令(commands)、配置项(configuration)等
开发步骤：
- 先写类型定义
- 实现核心逻辑
- 添加错误处理
- 进行功能测试
- 使用TypeScript开发，确保类型安全
- 遵循VSCode插件开发的标准结构：
- src/extension.ts 作为入口文件
- 合理划分功能模块
- 使用依赖注入管理服务
第四步：问题处理与调试
如果遇到问题：
- 查看相似功能的实现
- 不随意修改现有代码
- 保持架构的一致性
- 完整测试后再提交
- 检查VSCode的开发者工具输出
- 分析插件激活日志
- 使用VSCode内置的调试功能
特别关注的问题领域：
- 内存泄漏
- 插件激活性能
- API使用不当
- 异步操作处理
复杂问题解决方法：
- 使用VSCode内置的性能分析工具
- 检查插件的事件订阅和释放
- 验证API的使用是否符合最佳实践
- 提供多个解决方案，并说明各自的优缺点
第五步：质量保证
完成开发后：
- 运行完整的测试套件
- 检查代码覆盖率
- 验证插件在不同操作系统上的表现
- 确保符合VSCode插件发布标准
- 更新插件文档和更新日志
- 在 README.md 中提供清晰的安装和使用说明，更新项目文档 (如
README.md) 以反映最新进展
最佳实践遵循
- 使用 VSCode 推荐的 API 和模式
- 遵循 TypeScript 严格模式
- 实现优雅的错误处理
- 提供清晰的用户反馈
- 支持国际化
- 实现适当的遥测统计
- 注意插件的安全性考虑
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 · 91 lines · 834 tokens per session scan A 3368bfc28ef1
rule is a cursor rule published in the GitHub repository kelisiWu123/cursor-rules-wizard (7 stars, last pushed 1y ago), licensed MIT. It adds 834 tokens to every session, about $0.0042 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-31.
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.