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/x0c/corralWrote 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/x0c/corral/release-after-changes)<a href="https://agentmods.dev/rules/x0c/corral/release-after-changes"><img src="https://agentmods.dev/badge/rules/x0c/corral/release-after-changes/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/x0c/corral/release-after-changes"><img src="https://agentmods.dev/badge/rules/x0c/corral/release-after-changes.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.00305 | $0.00305 |
| Opus 5.5 | $0.00122 | $0.00122 |
| Sonnet 5.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 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
改完即发版
完成任何用户可见的功能、修复或行为改动后，必须发布新版本，不要只提交代码就结束。
流程
- 同步 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.
- 1mo ago 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 (3 stars, last pushed 9d ago), licensed MIT. It adds 305 tokens to every session, about $0.0012 per session on Opus 5.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
changesets
Changeset format and bump rules enforced by CI.
release-notes
Generate changelog entries and GitHub releases from git history. Categorizes commits into features, fixes, breaking changes, and docs. Supports conventional commits, PR-based grouping, and semantic versioning. Creates formatted CHANGELOG.md entries and GitHub releases.
release-checklist
What to update with each code change or version release.
bump-project-version
The user can provide version in one of three ways.
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.