agentmods.dev

releasing-operator

releasing-operator is a cursor rule for Cursor from jumpstarter-dev/jumpstarter. It costs 12 tokens per session (1,783 once invoked), scanned A, original, Apache-2.0.

Release instructions for publishing a new Kubernetes operator version to OpenShift's Operator Lifecycle Manager (OLM) and community operator repositories.

In plain words
What is it for?
Preparing bundle versions, setting image tags and release channels, generating release data, and submitting the operator to the relevant repositories.
Why use it?
They prevent version, image-tag, upgrade-order, and supported-OpenShift-version mistakes that can make an operator release fail or create conflicting upgrade paths.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Needs its repository: it reads a path above its own folder, which exists only inside the repository. The line is cd ../community-operators-prod && git push -f user jumpstarter-operator-release-X.Y.Z.

not rated 226repo +2 today A scan 12 tokens original Apache-2.0

Good fit Preparing bundle versions, setting image tags and release channels, generating release data, and submitting the operator to the relevant repositories.

Compare 6 cursor rules from other repositories ↓
View source ↗ jumpstarter-dev/jumpstarter jumpstarter.dev
Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/jumpstarter-dev/jumpstarter
agentmods
npx agentmods add rules/jumpstarter-dev/jumpstarter/releasing-operator

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.

agentmods badge for releasing-operator

README.md
[![agentmods](https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/releasing-operator/github.svg)](https://agentmods.dev/rules/jumpstarter-dev/jumpstarter/releasing-operator)
Your own site
<a href="https://agentmods.dev/rules/jumpstarter-dev/jumpstarter/releasing-operator"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/releasing-operator/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.

agentmods 80×15 button for releasing-operator

Your own site · 80×15
<a href="https://agentmods.dev/rules/jumpstarter-dev/jumpstarter/releasing-operator"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/releasing-operator.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 1,783 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00012 $0.01783
Opus 5.5 $0.00005 $0.00713
Sonnet 5.5 $0.00002 $0.00357
Haiku 4.5 $0.00001 $0.00178

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

Security

Grade A, and why

releasing-operator 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/releasing-operator.mdc · 131 lines

How it starts

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

Releasing the Jumpstarter Operator

This guide covers preparing and publishing a new operator release to OLM and community-operators repos.

Version Source of Truth

The operator bundle version is driven by variables in controller/deploy/operator/Makefile:

  • VERSION: The semver for the bundle (e.g. 0.8.1). This is NOT prefixed with v.
  • REPLACES: The previous OLM bundle this release upgrades from (e.g. jumpstarter-operator.v0.8.0). Note the OLM name uses a v prefix per OLM convention, but image tags do NOT. Important: This must point to the most recent published version in the channel, including release candidates. For example, if v0.8.1-rc.1 was published, then v0.8.1 must replace v0.8.1-rc.1 (not v0.8.0), otherwise OLM will report "multiple channel heads".
  • IMG: Defaults to $(IMAGE_TAG_BASE):$(VERSION), so all image references are automatically derived from VERSION. No need to pass IMG explicitly in most cases.
  • FBC_CHANNELS: Catalog channel (default alpha).
  • OPENSHIFT_VERSIONS: Red Hat OpenShift version range (e.g. v4.18-v4.21).
  • IMAGE_TAG_BASE: Registry prefix (quay.io/jumpstarter-dev/jumpstarter-operator).
  • BUNDLE_IMG / CATALOG_IMG: Also derived from IMAGE_TAG_BASE and VERSION automatically.

The config/manifests/bases/jumpstarter-operator.clusterserviceversion.yaml uses placeholder version 0.0.0 - the real version is injected by make bundle.

Image Tag Convention

This project tags container images without a v prefix: :0.8.1, NOT :v0.8.1. Since IMG defaults to $(IMAGE_TAG_BASE):$(VERSION), running make bundle or make contribute produces correct image references automatically. You can still override for custom builds:

make bundle IMG=quay.io/jumpstarter-dev/jumpstarter-operator:custom-tag

Files to Update When Bumping a Version

When preparing a new release version X.Y.Z, update these files together:

1. controller/deploy/operator/Makefile

  • VERSION ?= X.Y.Z
  • REPLACES ?= jumpstarter-operator.vPREVIOUS (the most recent version published to the OLM channel - including RCs. E.g. if v0.8.1-rc.1 was published, REPLACES must be jumpstarter-operator.v0.8.1-rc.1, not v0.8.0)
  • Optionally update OPENSHIFT_VERSIONS if the supported range changes

Read the full file on GitHub · 131 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.

  1. 1mo ago First seen · 131 lines · 12 tokens per session scan A dbd90464e863

Subscribe to this mod's changes

releasing-operator is a cursor rule published in the GitHub repository jumpstarter-dev/jumpstarter (226 stars, last pushed today), licensed Apache-2.0. It adds 12 tokens to every session and 1,783 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-30.

CI and CDDevOps and cloudGit and workflowReleasesboard-farmhardwarehardware-in-the-loophiltesting-framework
Related

Other cursor rules, from other repositories

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

cut-release

When the team is ready to ship a new version — version bumps, changelog finalization, dependency snapshots, and CI release trigger.

ahmadulhoq/agentskel · 27 tokens

sciclaw-papercuts

Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.

drpedapati/sciclaw · 607 tokens

dev-workflow

Monorepo developer workflow standards - mise tasks, git hooks, CI/CD, release automation.

gracefullight/stock-checker · 18 tokens

dev-workflow

Monorepo developer workflow standards - mise tasks, git hooks, CI/CD, release automation.

gracefullight/krds · 18 tokens