A set of release rules for a software project that uses semantic-release to publish versions automatically from commits merged into the main branch. Conventional Commits are a format such as `fix:` or `feat:` that tells the release system what kind of change was made.

Use it when making commits or reviewing release setup for this repository, especially when deciding whether a change should trigger a patch, minor, or major release.

It prevents manual version bumps, changelog edits, tags, releases, and package publishing that the automated workflow should handle. It also keeps commit messages consistent enough to determine the next version.

releases — Cursor rule for Cursor by MohtashamMurshid

Install

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.

Clone the repo

git clone --depth 1 https://github.com/MohtashamMurshid/md-to-docx

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/mohtashammurshid/md-to-docx/releases/github.svg)](https://agentmods.dev/rules/mohtashammurshid/md-to-docx/releases)

Your own site

<a href="https://agentmods.dev/rules/mohtashammurshid/md-to-docx/releases"><img src="https://agentmods.dev/badge/rules/mohtashammurshid/md-to-docx/releases/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/mohtashammurshid/md-to-docx/releases"><img src="https://agentmods.dev/badge/rules/mohtashammurshid/md-to-docx/releases.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 565 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00012	$0.00565
Opus 5	$0.00006	$0.00282
Sonnet 5	$0.00002	$0.00113
Haiku 4.5	$0.00001	$0.00056

Measured 12d ago against content hash 672ea389565b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

releases 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 12d 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.

.cursor/rules/releases.mdc · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Releases

This repo uses semantic-release on push to main. The agent MUST NOT do any of these manually:

Bump version in package.json / package-lock.json
Edit CHANGELOG.md (other than historical entries that already exist)
Create git tags (git tag v*)
Create GitHub Releases (gh release create)
Run npm publish

All of the above happen automatically from .github/workflows/release.yml driven by .releaserc.json.

Commit messages

Every commit merged to main MUST follow Conventional Commits:

Prefix	Effect
`fix:`	patch bump (x.y.Z)
`feat:`	minor bump (x.Y.0)
`feat!:` or body with `BREAKING CHANGE:`	major bump (X.0.0)
`chore:` `docs:` `style:` `refactor:` `perf:` `test:` `ci:` `build:`	no release

Examples:

feat: add syntax highlighting option to code blocks
fix(code-highlight): honor alias spellings in languages whitelist
chore: bump dev dependencies

Workflow facts

release.yml runs on Node 22 (semantic-release 25 requires Node ≥22.14).
setup-node in release.yml MUST NOT set registry-url — semantic-release manages npm auth itself via NPM_TOKEN. Setting registry-url causes a 401 on whoami.
ci.yml runs the test matrix on Node 18 + 20 to match downstream users.
Commits authored by the release bot end with [skip ci] and are filtered out by the if: guard in release.yml.

When the user asks to "cut a release" or "bump version"

Do NOT run npm version, edit package.json, or tag. Instead:

Verify there are releasable commits since the last v* tag (git log $(git describe --tags --abbrev=0)..HEAD --oneline).
If none, tell the user no fix:/feat: commits exist yet and ask what change they want to ship.
If releasable commits already exist on main, the release has either already happened or will on next push — no action needed.

See [RELEASING.md](../../RELEASING.md) for the full process and one-time repo setup.

Read the full file on GitHub · 52 lines

Changes

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.

12d ago First seen · 52 lines · 12 tokens per session scan A 672ea389565b

Subscribe to this mod's changes

releases is a cursor rule published in the GitHub repository MohtashamMurshid/md-to-docx (102 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 565 once invoked, about $0.0001 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-30.

Git and workflow Releases

monorepo-versioning

Internal peerDependency ranges and Changesets conventions for the SDK monorepo — avoid major-version cascades.

solvapay/solvapay-sdk · 0 tokens

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.

thatrebeccarae/claude-marketing · 50 tokens

releases