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.
npx agentmods add rules/jumpstarter-dev/jumpstarter/releasing-operatorgit clone --depth 1 https://github.com/jumpstarter-dev/jumpstarterWhat 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 | $0.00012 | $0.01783 |
| Opus 5 | $0.00006 | $0.00892 |
| Sonnet 5 | $0.00002 | $0.00357 |
| Haiku 4.5 | $0.00001 | $0.00178 |
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 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.
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 withv.REPLACES: The previous OLM bundle this release upgrades from (e.g.jumpstarter-operator.v0.8.0). Note the OLM name uses avprefix 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, ifv0.8.1-rc.1was published, thenv0.8.1must replacev0.8.1-rc.1(notv0.8.0), otherwise OLM will report "multiple channel heads".IMG: Defaults to$(IMAGE_TAG_BASE):$(VERSION), so all image references are automatically derived fromVERSION. No need to passIMGexplicitly in most cases.FBC_CHANNELS: Catalog channel (defaultalpha).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 fromIMAGE_TAG_BASEandVERSIONautomatically.
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.ZREPLACES ?= jumpstarter-operator.vPREVIOUS(the most recent version published to the OLM channel - including RCs. E.g. ifv0.8.1-rc.1was published, REPLACES must bejumpstarter-operator.v0.8.1-rc.1, notv0.8.0)- Optionally update
OPENSHIFT_VERSIONSif the supported range 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.
- yesterday First seen · 131 lines · 12 tokens per session scan A dbd90464e863
releasing-operator is a cursor rule published in the GitHub repository jumpstarter-dev/jumpstarter (214 stars, last pushed 2d ago), licensed Apache-2.0. It adds 12 tokens to every session and 1,783 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.
Other cursor rules, from other repositories
chiplab
Repository agent instructions for chiplab.
open-locker-domain
This project implements a digital locker sharing system for lending physical items. Follow these domain-specific conventions.
monorepo-architecture
This is a monorepo containing multiple interconnected components for the Open-Locker IoT system.
scramble-openapi
REST API OpenAPI Documentation Guidelines.
adr-decision-required
Require ADRs for architecture-significant decisions.
modbus-integration
The backend does not communicate with Modbus hardware directly. Physical locker control runs in locker-client (Raspberry Pi), which talks to hardware via Modbus and reports status back to the backend over MQTT.