A set of project rules for automated checks, pull requests, and software releases. CI/CD means automatically checking code and publishing releases through a repeatable process.

It covers checks such as type-checking, linting, formatting, building, and package testing across Node.js versions. It also documents GitHub Release publishing, pre-release tags, dependency updates, and generated files that should not be edited in pull requests.

It tells contributors and coding agents what must pass before code is merged and how releases are published, reducing failed builds and inconsistent release steps.

ci-cd — Cursor rule for Cursor by evtapps/ditto-mcp

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/evtapps/ditto-mcp

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/evtapps/ditto-mcp/ci-cd/github.svg)](https://agentmods.dev/rules/evtapps/ditto-mcp/ci-cd)

Your own site

<a href="https://agentmods.dev/rules/evtapps/ditto-mcp/ci-cd"><img src="https://agentmods.dev/badge/rules/evtapps/ditto-mcp/ci-cd/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/evtapps/ditto-mcp/ci-cd"><img src="https://agentmods.dev/badge/rules/evtapps/ditto-mcp/ci-cd.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 121 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.00010	$0.00121
Opus 5.5	$0.00004	$0.00048
Sonnet 5.5	$0.00002	$0.00024
Haiku 4.5	$0.00001	$0.00012

Measured 1mo ago against content hash 1ce40a2e01ef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ci-cd 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.

.cursor/rules/ci-cd.mdc · 11 lines

What it actually says

CI/CD & Releases

Build checks run on Node 18/20/22: type-check, lint, format:check, build, pack dry-run.
Any PR must pass CI before merge.
Release workflow publishes when a GitHub Release is published; uses NPM_TOKEN secret.
Pre-releases publish under canary tag.
Dependabot runs monthly for npm, docker, and actions.
Do not modify dist/* in PRs; it is built on publish.

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.

1mo ago First seen · 11 lines · 10 tokens per session scan A 1ce40a2e01ef

Subscribe to this mod's changes

ci-cd is a cursor rule published in the GitHub repository evtapps/ditto-mcp (0 stars, last pushed 10mo ago), licensed MIT. It adds 10 tokens to every session and 121 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.

CI and CD DevOps and cloud Git and workflow Releases

releasing-operator

when the user is releasing a new version of the Kubernetes operator.

jumpstarter-dev/jumpstarter · 12 tokens

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.

louisbrulenaudet/monorepo-template · 0 tokens

ci-cd-workflows

This rule provides guidance on the CI/CD pipeline, GitHub Actions workflows (defined in .github/workflows/), custom actions (in .github/actions/), versioning strategies, and release processes. Use this rule if the query involves CI/CD, build/test issues, release procedures, versioning questions, or if it references…

mondaycom/vibe · 0 tokens

ci-cd