host-controller

A set of rules for Forklift’s host controller, which manages ESXi hosts used during vSphere migrations. ESXi is VMware’s server software, and vSphere is VMware’s management platform.

In plain words
What is it for?
Use it when changing host validation, ESXi connectivity checks, credential watches, provider references, or migration inventory handling.
Why use it?
It clarifies how host settings, credentials, providers, and inventory changes are checked, including which provider types are supported.

Cursor rule for Cursor

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/host-controller
Clone the repo
git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 954 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.

ModelPer sessionOnce invoked
Fable 5 $0.00013 $0.00954
Opus 5 $0.00006 $0.00477
Sonnet 5 $0.00003 $0.00191
Haiku 4.5 $0.00001 $0.00095

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

Security

Grade A, and why

host-controller 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/infrastructure/host-controller.mdc · 94 lines

How it starts

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

Host Controller

Source: pkg/controller/host/

Purpose

The Host CRD represents an ESXi host used for direct disk transfer during vSphere migrations. The controller validates the host configuration and tests connectivity to the ESXi SDK endpoint.

Only vSphere providers are supported. All other provider types set a TypeNotValid blocker condition. Non-vSphere handler implementations (oVirt, OCP, OpenStack, OVA, HyperV) are no-ops.

Watched Resources

Resource Watch Type Purpose
Host Primary Reconcile on create/update/delete
Provider Reference Re-reconcile hosts when their provider changes; sets up inventory watches
Secret Reference Re-reconcile when host credentials change
Channel Generic events Receives events from inventory watches (host changes in vSphere)

Reconciliation Flow

Fetch Host CR
  → BeginStagingConditions
  → validate()
    → validateProvider()   — provider exists, is reconciled, and is vSphere
    → validateRef()        — host ref (ID/Name) resolves in provider inventory
    → validateIp()         — ipAddress is set
    → validateSecret()     — secret exists, has "user" + "password" keys, TLS validates
    → Set Validated condition
    → testConnection()     — connect to ESXi SDK, check maintenance/health
  → Set Ready if no blockers AND ConnectionTestSucceeded
  → EndStagingConditions
  → Record events, update status
  → If ConnectionTestFailed: requeue after 15 minutes

Conditions

Condition Category When Set
Validated Advisory All validations pass
RefNotValid Critical Host ref not set, not found in inventory, or ambiguous
SecretNotValid Critical Secret missing, not found, missing keys, or TLS failure
TypeNotValid Critical Provider is not vSphere
IpNotValid Critical ipAddress field is empty
ConnectionTestSucceeded Required ESXi SDK connection successful
ConnectionTestFailed Critical Cannot connect to ESXi host
InMaintenance Critical ESXi host is in maintenance mode
NotHealthy Critical ESXi host status is not "green"
Ready Required No blockers + connection test succeeded

Read the full file on GitHub · 94 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. 2d ago First seen · 94 lines · 13 tokens per session scan A 9a296e9d57b8

Subscribe to this mod's changes

host-controller 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 13 tokens to every session and 954 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.