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/usrrname/cursorrulesWrote 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/usrrname/cursorrules/release-changelog-auto)<a href="https://agentmods.dev/rules/usrrname/cursorrules/release-changelog-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/release-changelog-auto/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/usrrname/cursorrules/release-changelog-auto"><img src="https://agentmods.dev/badge/rules/usrrname/cursorrules/release-changelog-auto.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.00000 | $0.01405 |
| Opus 5.5 | $0.00000 | $0.00562 |
| Sonnet 5.5 | $0.00000 | $0.00281 |
| Haiku 4.5 | $0.00000 | $0.00140 |
Grade A, and why
release-changelog-auto 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Changelog Generation
Critical Rules
- Must validate that changelog can be generated before proceeding
- Must backup existing changelog.md if it exists
- Must check if existing changelog follows Keep a Changelog format
- Must call the existing changelog-generator-manual rule for actual generation
- Must preserve existing changelog content when possible
- Must provide clear feedback about changelog generation status
filters:
- type: content pattern: "(release|version|tag|bump|publish|deploy).*(create|make|generate|prepare|ready)"
- type: git_branch pattern: "^(?!main$|master$).*$"
- type: event pattern: "chat_start|chat_response"
actions:
-
type: generate content: |
📝 Changelog Generation Process
I'll validate the environment and generate a comprehensive changelog for your release.
- Validate Changelog Generation:
echo "🔄 Now generating comprehensive changelog..." # Backup existing changelog if it exists if [ -f "changelog.md" ]; then cp changelog.md changelog.md.backup echo "📋 Backed up existing changelog.md" # Check if existing changelog has proper structure if grep -q "## \[Unreleased\]" changelog.md; then echo "✅ Existing changelog has proper structure, will preserve content" PRESERVE_EXISTING=true else echo "⚠️ Existing changelog doesn't follow Keep a Changelog format" echo "Will create new changelog with existing content as reference" PRESERVE_EXISTING=false fi else echo "📝 No existing changelog.md found, creating new one" PRESERVE_EXISTING=false fi # Get all git tags sorted by version ALL_TAGS=$(git tag --sort=-version:refname) # Get commits since last tag (unreleased changes) UNRELEASED_COMMITS=$(git log --oneline --no-merges $(git describe --tags --abbrev=0 2>/dev/null || echo "")..HEAD) echo "📊 Changelog generation summary:" echo " - Total git tags: $(echo "$ALL_TAGS" | wc -l | tr -d ' ')" echo " - Unreleased commits: $(echo "$UNRELEASED_COMMITS" | wc -l | tr -d ' ')" echo " - Preserve existing: $PRESERVE_EXISTING"
- Validate Changelog Generation:
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 · 164 lines · 0 tokens per session scan A cf37bb2d05db
release-changelog-auto is a cursor rule published in the GitHub repository usrrname/cursorrules (11 stars, last pushed 6mo ago), licensed ISC. It costs nothing until one of its globs matches a file; then it loads 1,405 tokens. 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
git-workflow
Git workflow: commits, branches, PRs, history management.
git-master
Git operations — clean commits, PR prep, conflict resolution, change summaries.
release
Changesets release pipeline - version PR and its dispatched CI check, shared vX.Y.Z tag, CI gate before tagging, release:check gate, Dependabot changesets, no npm publish, GITHUBTOKEN tag trigger limitation.
changesets
Writing changesets - when one is needed, apps-only frontmatter, bump levels for deployed apps, summary style, non-interactive creation.
cd
GitHub Actions CD - called by release.yml after the tag, no push-tags trigger, cf workers versions create then a 100% deployment in deployOrder, scoped API token on the production environment, GitHub-owned deployment record.
changeset
Guidelines for using Changesets (npm run changeset) to manage versioning and changelogs.