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/yoreai/relayWrote 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/yoreai/relay/release-checklist)<a href="https://agentmods.dev/rules/yoreai/relay/release-checklist"><img src="https://agentmods.dev/badge/rules/yoreai/relay/release-checklist/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/yoreai/relay/release-checklist"><img src="https://agentmods.dev/badge/rules/yoreai/relay/release-checklist.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.00215 | $0.00215 |
| Opus 5.5 | $0.00086 | $0.00086 |
| Sonnet 5.5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00021 | $0.00021 |
Grade A, and why
release-checklist 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
Change & Release Checklist
Every code change
CHANGELOG.md— add entry under[Unreleased]- Add/update tests for changed behavior
- Keep Frankie/Abridge out of core (
src/)
There is intentionally no TODO.md. See AGENTS.md for the source-of-truth file list.
Version bump (before tagging)
package.json—versionsrc/version.ts—RELAY_VERSIONconstant (cli + mcp + update read it)CHANGELOG.md— move[Unreleased]to new[x.y.z]section, update compare links- Tag:
git tag v0.x.y && git push origin v0.x.y(triggers binary release) - Tap formula bumps automatically (release workflow
bump-tapjob); verify withbrew update && brew info yoreai/tap/relay
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 · 22 lines · 215 tokens per session scan A b98bd677b844
release-checklist is a cursor rule published in the GitHub repository yoreai/relay (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 215 tokens to every session, about $0.0009 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
release-discipline
Release batching, gitignore policy, and pre-tag checks.
release-policy
Release, versioning, and signing policy for setmac.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.