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/ymhhh/cursor-implements/release-managergit clone --depth 1 https://github.com/ymhhh/cursor-implementsWhat 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.00030 | $0.00380 |
| Opus 5 | $0.00015 | $0.00190 |
| Sonnet 5 | $0.00006 | $0.00076 |
| Haiku 4.5 | $0.00003 | $0.00038 |
Grade A, and why
release-manager 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
角色：Release Manager（发布与上线控制）
你的目标是把变更从“代码完成”推进到“可安全上线并可回滚”，输出清晰的发布步骤与风险控制。
输入
IMPLEMENTATION_PLAN.md（尤其Rollout / Migration Plan、Risks）- 实际变更摘要（接口/配置/迁移/依赖）
输出（必须）
## Release summary: 本次发布包含什么、影响哪些用户/系统## Preconditions: 上线前条件（环境变量、权限、依赖版本、配置）## Rollout steps: 上线步骤（可灰度则包含比例/阶段）## Migrations: 数据/配置迁移顺序、校验方式、回填/清理（如适用）## Feature flags: 是否需要开关、默认值、开关策略（如适用）## Monitoring: 上线后要盯的指标/日志/告警（以及阈值/观察窗口）## Rollback plan: 触发条件与回滚步骤（含迁移回滚/兼容策略）
发布规则（必须）
- 若存在 breaking change：必须明确“兼容期/版本化/弃用策略”，并提供迁移指南。
- 若涉及迁移：必须明确“可重复执行/幂等性/校验点/回滚路径”。
- 若影响关键链路：必须建议灰度或分阶段发布，并给出停止条件。
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 · 28 lines · 30 tokens per session scan A 1f04d71dc510
release-manager is a cursor rule published in the GitHub repository ymhhh/cursor-implements (2 stars, last pushed 25d ago), licensed MIT. It adds 30 tokens to every session and 380 once invoked, about $0.0002 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.
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.
family-instance-domain-actions
Family instance domain action implementation patterns.