A set of rules describing how the Forklift Operator deploys and manages Forklift, a system for moving virtual machines between environments. It explains how a Kubernetes custom resource, called ForkliftController, maps settings to deployment options.

Use it when changing ForkliftController settings, feature flags, container images, or deployment behavior.

It helps developers understand which configuration fields control Forklift features and how the operator reconciles the system's components.

operator — Cursor rule by kubev2v

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.

agentmods

npx agentmods add rules/kubev2v/forklift-console-plugin/operator

Clone the repo

git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

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

When invoked 2,549 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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	$0.00020	$0.02549
Opus 5	$0.00010	$0.01274
Sonnet 5	$0.00004	$0.00510
Haiku 4.5	$0.00002	$0.00255

Measured 2d ago against content hash d9347b0bcc73, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 2d 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/backend/operator/operator.mdc · 227 lines

How it starts

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

Forklift Operator

Analyzed from commit: a976d24b6 on 2026-05-04

Overview

The Forklift operator is an Ansible-based operator (operator-sdk) that watches the ForkliftController CRD and reconciles all Forklift components into the target namespace. It uses a single Ansible role (forkliftcontroller) with Jinja2 templates.

ForkliftController CRD

Group: forklift.konveyor.io, Version: v1beta1, Kind: ForkliftController
Single watched resource defined in operator/watches.yaml
Has a finalizer (forklift.konveyor.io/finalizer) for cleanup on deletion
The CR's .spec fields map to Ansible variables that override defaults in roles/forkliftcontroller/defaults/main.yml

Key Configurable Fields (CR spec → Ansible var)

CR field	Ansible variable	Default
`feature_volume_populator`	`feature_volume_populator`	`true`
`feature_copy_offload`	`feature_copy_offload`	`true`
`feature_ocp_live_migration`	`feature_ocp_live_migration`	`true`
`feature_vmware_system_serial_number`	`feature_vmware_system_serial_number`	`true`
`feature_vsphere_vmware_driver_removal`	`feature_vsphere_vmware_driver_removal`	`false`
`feature_ui_plugin`	`feature_ui_plugin`	`true`
`feature_validation`	`feature_validation`	`true`
`feature_cli_download`	`feature_cli_download`	`true`
`feature_ova_appliance_management`	`feature_ova_appliance_management`	`true`
`controller_max_vm_inflight`	`controller_max_vm_inflight`	`20`
`controller_precopy_interval`	`controller_precopy_interval`	`60`
`controller_log_level`	`controller_log_level`	`3`

Feature Flags

Feature flags flow from the ForkliftController CR through Ansible into environment variables on the controller pod:

ForkliftController CR spec
  → Ansible defaults/main.yml
    → Jinja2 template (deployment-controller.yml.j2)
      → Pod env vars (FEATURE_*)
        → Go pkg/settings/features.go loads them

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

2d ago First seen · 227 lines · 20 tokens per session scan A d9347b0bcc73

Subscribe to this mod's changes

operator is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 2,549 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.

Backend and APIs DevOps and cloud

operator

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Forklift Operator

Overview

ForkliftController CRD

Key Configurable Fields (CR spec → Ansible var)

Feature Flags

What this file has done since we first saw it

Other cursor rules, from other repositories

angular-20

dev-standard

typescript

coolify-ai-docs

python_lib

specs