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/evtapps/ditto-mcpWrote 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/evtapps/ditto-mcp/versioning)<a href="https://agentmods.dev/rules/evtapps/ditto-mcp/versioning"><img src="https://agentmods.dev/badge/rules/evtapps/ditto-mcp/versioning/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/evtapps/ditto-mcp/versioning"><img src="https://agentmods.dev/badge/rules/evtapps/ditto-mcp/versioning.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.00006 | $0.00357 |
| Opus 5.5 | $0.00002 | $0.00143 |
| Sonnet 5.5 | $0.00001 | $0.00071 |
| Haiku 4.5 | $0.00001 | $0.00036 |
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 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
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.jsonviasrc/utils/version.ts. - Override for custom builds: set
MCP_SERVER_VERSIONenv. Fallback when unavailable:0.0.0-dev. - The CLI supports
--versionand reports the same value.
Build & Pack
prepackbuilds automatically before publish. Do not publish without a clean build.- Confirm
npm pack --dry-runonly includesdist,README.md,LICENSE,CHANGELOG.md.
Releases & Dist-tags
- Pre-releases: publish under the
canarydist-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 publishmay be required locally (provide OTP).
Validation
- Verify tags and versions:
npm view ditto-mcp-server@<version> versionnpm dist-tag ls ditto-mcp-server
- Fresh install smoke test:
npm i ditto-mcp-server@<tag>and runnpx ditto-mcp --version.
- Inspector E2E:
npx @modelcontextprotocol/inspector npx ditto-mcp-server@<tag>.
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 · 35 lines · 6 tokens per session scan A d1150dd5b505
versioning is a cursor rule published in the GitHub repository evtapps/ditto-mcp (0 stars, last pushed 10mo ago), licensed MIT. It adds 6 tokens to every session and 357 once invoked, about $0.0000 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
changesets
Changeset format and bump rules enforced by CI.
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.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
release-checklist
What to update with each code change or version release.
github-cli-guide
A guide on how to use the Github CLI (gh cli) especially related to creating issues via the CLI.
release-policy
Release, versioning, and signing policy for setmac.