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/thatrebeccarae/claude-marketingWrote 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/thatrebeccarae/claude-marketing/release-notes)<a href="https://agentmods.dev/rules/thatrebeccarae/claude-marketing/release-notes"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/release-notes/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/thatrebeccarae/claude-marketing/release-notes"><img src="https://agentmods.dev/badge/rules/thatrebeccarae/claude-marketing/release-notes.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.00050 | $0.02659 |
| Opus 5.5 | $0.00020 | $0.01064 |
| Sonnet 5.5 | $0.00010 | $0.00532 |
| Haiku 4.5 | $0.00005 | $0.00266 |
Grade A, and why
release-notes 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.
How it starts
The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
release-notes
Generate changelog entries and GitHub releases from git history.
When to Use
- Cutting a release: You have commits ready to ship and need a changelog entry and/or GitHub release.
- Monthly changelog update: You maintain a regular changelog cadence and need to capture everything since the last entry.
- Retroactive changelog: An existing project has no CHANGELOG.md and you want to generate one from the full git history.
Usage
Generate a changelog entry
/release-notes changelog [repo-path]
Reads commits since the last tag, categorizes them, and prepends a new entry to CHANGELOG.md.
Create a changelog entry and GitHub release
/release-notes release [repo-path] [version]
Does everything changelog does, then creates a GitHub release via gh release create. If version is omitted, a version is suggested based on the changes detected.
Retroactively generate a full changelog
/release-notes init [repo-path]
Walks the entire tag history (or full commit history if untagged) and generates a complete CHANGELOG.md from scratch.
Procedure
Step 1 — Find the last tag or release
Run git describe --tags --abbrev=0 to find the most recent tag. If no tags exist, use the initial commit as the starting point. Cross-reference with gh release list --limit 1 to check for GitHub releases that may differ from local tags.
Step 2 — Collect commits since last tag
git log <last-tag>..HEAD --pretty=format:"%H %s" --no-merges
Parse each commit message for conventional commit prefixes (type(scope): description). Record the raw message for commits that do not follow conventional format.
Step 3 — Check merged PRs
gh pr list --state merged --search "merged:>YYYY-MM-DD" --json number,title,labels,mergedAt --limit 200
Use the date of the last tag as the cutoff. Cross-reference PR titles with commit messages to avoid duplicates. PR titles often provide cleaner descriptions than commit messages — prefer the PR title when a commit is associated with a merged PR.
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 · 351 lines · 50 tokens per session scan A 17c662ed4c20
release-notes is a cursor rule published in the GitHub repository thatrebeccarae/claude-marketing (173 stars, last pushed 5mo ago), licensed MIT. It adds 50 tokens to every session and 2,659 once invoked, about $0.0002 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-30.
Other cursor rules, from other repositories
github-cli
Apply when using the gh CLI to manage pull requests, issues, releases, or CI workflows on GitHub.
git-pr-reviewer
Pull Request (PR) creation and code review standards with constructive feedback and merge strategies. / TR: Pull Request (PR) oluşturma ve kod inceleme (code review) süreçleri için standartlar ve yapıcı geri bildirim.
branch-finishing
Apply when closing out a feature branch — pre-merge checklist, rebase, CI verification, cleanup, and post-merge steps.
git-conventions
Apply when committing, branching, or opening a pull request. Conventional commit format, branch naming, PR scope.
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.