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/plan-adapters)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/plan-adapters"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/plan-adapters/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/plan-adapters"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/plan-adapters.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.00014 | $0.05604 |
| Opus 5.5 | $0.00006 | $0.02242 |
| Sonnet 5.5 | $0.00003 | $0.01121 |
| Haiku 4.5 | $0.00001 | $0.00560 |
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 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Adapters
Analyzed from commit:
baf9c7bccon2026-09-17Source paths:pkg/controller/plan/adapter/,pkg/provider/azure/controller/adapter/,pkg/provider/ec2/controller/adapter/
Package Purpose
The plan adapter pattern abstracts provider-specific migration logic behind a uniform interface. Each source provider implements the same Adapter factory (Builder, Client, Validator, DestinationClient, Ensurer) so the plan controller and migrator can orchestrate migrations without provider-specific branching. Provider-specific Builder/Client/Validator code lives either under pkg/controller/plan/adapter/<provider>/ (legacy in-tree providers) or under pkg/provider/<provider>/controller/ (Azure, EC2 — out-of-tree layout with dedicated migrator/scheduler packages).
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() // pkg/provider/ec2/controller/adapter
case api.HyperV: adapter = &hyperv.Adapter{}
case api.Nutanix: adapter = &nutanix.Adapter{}
case api.Azure: adapter = azureadapter.New() // pkg/provider/azure/controller/adapter
default: err = liberr.New("provider not supported.")
}
}
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 five sub-interfaces. All methods receive *plancontext.Context (plan execution context with source/destination provider refs, secrets, inventory clients, and plan spec).
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 · +91 lines 1faa9d361f36
- 1mo 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 today), licensed Apache-2.0. It adds 14 tokens to every session and 5,604 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
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.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).
control-plane-descriptors
Control plane descriptor and instance implementation patterns.