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/kubev2v/forklift-console-plugin/plan-adaptersgit clone --depth 1 https://github.com/kubev2v/forklift-console-pluginWhat 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.00014 | $0.03593 |
| Opus 5 | $0.00007 | $0.01796 |
| Sonnet 5 | $0.00003 | $0.00719 |
| Haiku 4.5 | $0.00001 | $0.00359 |
Grade A, and why
plan-adapters 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.
How it starts
The opening of the file, as written. The whole thing — 287 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Adapters
Analyzed from commit:
412c71822on2026-05-04
Overview
The plan adapter pattern abstracts provider-specific migration logic behind a uniform interface. Each source provider (vSphere, oVirt, OpenStack, OVA, Hyper-V, EC2, OpenShift) implements the same set of interfaces so the plan controller can orchestrate migrations without provider-specific branching.
Source: pkg/controller/plan/adapter/
Factory Pattern
pkg/controller/plan/adapter/doc.go contains the New() factory that returns the correct adapter based on provider.Type():
func New(provider *api.Provider) (adapter Adapter, err error) {
switch provider.Type() {
case api.VSphere: adapter = &vsphere.Adapter{}
case api.OVirt: adapter = &ovirt.Adapter{}
case api.OpenStack: adapter = &openstack.Adapter{}
case api.OpenShift: adapter = &ocp.Adapter{}
case api.Ova: adapter = &ova.Adapter{} // alias for ovfbase.Adapter
case api.EC2: adapter = ec2adapter.New() // separate package
case api.HyperV: adapter = &hyperv.Adapter{}
}
}
The package re-exports base types so consumers import from adapter directly:
Adapter, Builder, Ensurer, Client, Validator, DestinationClient.
Core Interfaces
Adapter (top-level factory)
Each provider's Adapter struct implements this interface to construct the four sub-interfaces. All methods receive *plancontext.Context (the plan execution context with source/destination provider refs, secrets, inventory clients, and plan spec).
type Adapter interface {
Builder(ctx *plancontext.Context) (Builder, error)
Client(ctx *plancontext.Context) (Client, error)
Validator(ctx *plancontext.Context) (Validator, error)
DestinationClient(ctx *plancontext.Context) (DestinationClient, error)
Ensurer(ctx *plancontext.Context) (Ensurer, error)
}
Builder — constructs migration K8s resources
The Builder translates source VM inventory into destination Kubernetes objects (DataVolumes, PVCs, VirtualMachine specs, Secrets, ConfigMaps).
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 · 287 lines · 14 tokens per session scan A 602b6f772db7
plan-adapters is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 14 tokens to every session and 3,593 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
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.