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/x0c/corral/release-after-changesgit clone --depth 1 https://github.com/x0c/corralWhat 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.00305 | $0.00305 |
| Opus 5 | $0.00152 | $0.00152 |
| Sonnet 5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00030 | $0.00030 |
Grade A, and why
release-after-changes 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 yesterday.
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
改完即发版
完成任何用户可见的功能、修复或行为改动后，必须发布新版本，不要只提交代码就结束。
流程
- 同步 bump：
pyproject.toml、Cargo.toml、Cargo.lock、src/corral/__init__.py（补丁位递增） - 跑验证：完整套件每个版本只跑一次；成功后记戳，推送/收尾若产品代码未改不再整套重跑
- 提交：
release: vX.Y.Z <简述> - 打 annotated tag：
git tag -a vX.Y.Z -m "vX.Y.Z" - 推送：
git push github main+ tag，以及origin同名分支与 tag gh release create vX.Y.Z --repo x0c/corral --title vX.Y.Z --notes ...- 核对
releases/latest的tag_name等于刚发的版本
细则见 docs/MAINTAINER_GUIDE.md「开源发布」。纯文档/规则整理且无产品行为变化时可不发版；有疑义时默认发版。
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.
- yesterday First seen · 21 lines · 305 tokens per session scan A 6715eb8d7788
release-after-changes is a cursor rule published in the GitHub repository x0c/corral (2 stars, last pushed yesterday), licensed MIT. It adds 305 tokens to every session, about $0.0015 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
use-bun-instead-of-node-vite-npm-pnpm
../../CLAUDE.md.
alive-analysis
ALIVE analysis workflow for structured data analysis. Use when user discusses data analysis, metrics, A/B tests, experiments, monitoring, or asks analytical questions like 'why did X drop' or 'can we predict Y'.
always
Hard-coded constants live in const blocks.
intelligent
RPC service conventions.
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.