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/jumpstarter-dev/jumpstarterWrote 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/jumpstarter-dev/jumpstarter/working-with-operator)<a href="https://agentmods.dev/rules/jumpstarter-dev/jumpstarter/working-with-operator"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/working-with-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.
<a href="https://agentmods.dev/rules/jumpstarter-dev/jumpstarter/working-with-operator"><img src="https://agentmods.dev/badge/rules/jumpstarter-dev/jumpstarter/working-with-operator.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.00015 | $0.01385 |
| Opus 5.5 | $0.00006 | $0.00554 |
| Sonnet 5.5 | $0.00003 | $0.00277 |
| Haiku 4.5 | $0.00002 | $0.00138 |
Grade A, and why
working-with-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.
How it starts
The opening of the file, as written. The whole thing — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Working with the Jumpstarter Operator
The Jumpstarter operator is a Kubernetes operator that manages Jumpstarter deployments. It is located in controller/deploy/operator/.
Directory Structure
controller/
├── deploy/
│ ├── operator/ # Operator code
│ │ ├── api/v1alpha1/ # CRD type definitions
│ │ │ └── jumpstarter_types.go # Main types file
│ │ ├── internal/controller/ # Controller logic
│ │ │ └── jumpstarter/
│ │ │ ├── jumpstarter_controller.go # Main reconciler
│ │ │ ├── endpoints/ # Endpoint handling (routes, ingress, etc.)
│ │ │ └── rbac.go # RBAC reconciliation
│ │ ├── config/ # Kustomize configurations
│ │ │ ├── crd/bases/ # Generated CRD YAML
│ │ │ └── samples/ # Sample CR files
│ │ ├── bundle/ # OLM bundle manifests
│ │ ├── test/e2e/ # E2E tests
│ │ └── Makefile # Operator-specific make targets
├── api/ # Jumpstarter core CRDs (Client, Exporter, Lease, etc.)
├── internal/ # Controller business logic
│ └── config/ # Config structs used by controller
└── Makefile # Top-level controller make targets
Key Files
api/v1alpha1/jumpstarter_types.go: Defines theJumpstarterCRD spec and statusinternal/controller/jumpstarter/jumpstarter_controller.go: Main reconciliation logicinternal/controller/jumpstarter/jumpstarter_controller.go:buildConfig(): Translates CRD spec to internal config format for ConfigMaps
Development Workflow
After Modifying CRD Types
When you change jumpstarter_types.go, you MUST regenerate code:
cd controller/deploy/operator
make manifests generate
This will:
- Regenerate CRD YAML in
config/crd/bases/ - Regenerate
DeepCopymethods inzz_generated.deepcopy.go
Building
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 · 185 lines · 15 tokens per session scan A 43603442d23d
working-with-operator is a cursor rule published in the GitHub repository jumpstarter-dev/jumpstarter (226 stars, last pushed today), licensed Apache-2.0. It adds 15 tokens to every session and 1,385 once invoked, about $0.0001 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.
Other cursor rules, from other repositories
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
viberaven-deploy
Apply before changing Vercel config or deploy CI workflows.
platform-engineer
Cursor rule "platform-engineer" from ulises-jeremias/agent-toolkit, covering platform engineer, responsibility, main skill domains, when invoked and delegate to skills.
infrastructure
Terraform infrastructure-as-code standards for multi-cloud (AWS, GCP, Azure, OCI) provisioning.
devops-engineer-intelligent
DevOps and infrastructure specialist for CI/CD pipelines, deployment automation, and cloud operations. Apply this rule when working on continuous integration/continuous deployment setup, infrastructure as code (Terraform, CloudFormation, Ansible), Docker containerization, Kubernetes orchestration, cloud platform…
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.