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/kubev2v/forklift-console-pluginWrote 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/kubev2v/forklift-console-plugin/host-controller)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/host-controller"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/host-controller/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/kubev2v/forklift-console-plugin/host-controller"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/host-controller.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.00013 | $0.01689 |
| Opus 5.5 | $0.00005 | $0.00676 |
| Sonnet 5.5 | $0.00003 | $0.00338 |
| Haiku 4.5 | $0.00001 | $0.00169 |
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 29d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Host Controller
Analyzed from commit:
baf9c7bcc307ed9358ad59886a5536366a050012on 2026-09-17 Source paths:pkg/controller/host/
Package Purpose
The Host CRD represents an ESXi host used for direct disk transfer during vSphere migrations. The controller validates the host configuration (provider, inventory ref, IP, credentials) and tests connectivity to the ESXi SDK endpoint. Only vSphere providers are supported for host operations — all other provider types set a TypeNotValid blocker condition. Non-vSphere inventory handlers are no-ops.
Key Types and Structs
HostSpec (pkg/apis/forklift/v1beta1/host.go)
type HostSpec struct {
ref.Ref `json:",inline"` // inventory host ref (id/name)
Provider core.ObjectReference // vSphere Provider ref
IpAddress string // ESXi IP for disk transfer
Secret core.ObjectReference // credentials Secret
}
Reconciler (pkg/controller/host/controller.go)
type Reconciler struct {
base.Reconciler
}
Runtime fields populated during validation: host.Provider.Source (Provider CR), host.Secret (Secret CR).
Handler factory (pkg/controller/host/handler/doc.go)
Provider-type dispatch for inventory watches:
| Provider type | Handler | Behavior |
|---|---|---|
vSphere |
handler/vsphere |
Watches vsphere.Host inventory model |
oVirt, OpenStack, Ova, HyperV, OpenShift |
per-provider handlers | No-op Watch() |
EC2, Azure |
NoOpHostHandler |
No host-level operations |
Nutanix |
handler/nutanix |
No-op (no ESXi-style hosts) |
Interfaces and Implementations
type Handler interface {
Watch(m *handler.WatchManager) error
}
- vSphere handler (
handler/vsphere/handler.go): implements inventory event callbacks (Created,Updated,Deleted) and enqueues reconcile events for matching Host CRs. - ProviderPredicate (
predicate.go): embedshandler.WatchManager; callshandler.New()andWatch()when a Provider becomes Ready.
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.
- 29d ago Changed · +87 lines ccd81f27bdb6
- 1mo ago First seen · 94 lines · 13 tokens per session scan A 9a296e9d57b8
host-controller is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 1,689 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.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.