versioning

Rules for numbering, building, publishing, and checking releases of an npm package. SemVer is a versioning system where major, minor, and patch numbers signal the type of change.

In plain words
What is it for?
Use it when releasing the package, choosing a version or dist-tag, preparing a canary build, and checking the published result.
Why use it?
It keeps published versions understandable and helps catch incomplete builds, incorrect package contents, and broken fresh installs.

Cursor rule for Cursor

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.

agentmods
npx agentmods add rules/evtapps/ditto-mcp/versioning
Clone the repo
git clone --depth 1 https://github.com/evtapps/ditto-mcp

Made for: Cursor.

Per session 6 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 357 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00006 $0.00357
Opus 5 $0.00003 $0.00179
Sonnet 5 $0.00001 $0.00071
Haiku 4.5 $0.00001 $0.00036

Measured yesterday against content hash d1150dd5b505, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

versioning 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 yesterday.

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/versioning.mdc · 35 lines

What it actually says

Versioning & Publishing

SemVer

  • Follow SemVer: breaking changes → major, new features → minor, fixes → patch.

Single Source of Truth for Version

  • The runtime server version is derived from package.json via src/utils/version.ts.
  • Override for custom builds: set MCP_SERVER_VERSION env. Fallback when unavailable: 0.0.0-dev.
  • The CLI supports --version and reports the same value.

Build & Pack

  • prepack builds automatically before publish. Do not publish without a clean build.
  • Confirm npm pack --dry-run only includes dist, README.md, LICENSE, CHANGELOG.md.

Releases & Dist-tags

  • Pre-releases: publish under the canary dist-tag (e.g., 0.1.2-canary.0).
  • Stable: publish under latest (e.g., 0.1.2).
  • Recommended: use GitHub Releases to trigger the publish pipeline with NPM_TOKEN.
  • 2FA accounts: interactive npm publish may be required locally (provide OTP).

Validation

  • Verify tags and versions:
    • npm view ditto-mcp-server@<version> version
    • npm dist-tag ls ditto-mcp-server
  • Fresh install smoke test:
    • npm i ditto-mcp-server@<tag> and run npx ditto-mcp --version.
  • Inspector E2E: npx @modelcontextprotocol/inspector npx ditto-mcp-server@<tag>.
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.

  1. yesterday First seen · 35 lines · 6 tokens per session scan A d1150dd5b505

Subscribe to this mod's changes

versioning is a cursor rule published in the GitHub repository evtapps/ditto-mcp (0 stars, last pushed 9mo ago), licensed MIT. It adds 6 tokens to every session and 357 once invoked, about $0.0000 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-31.