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/migration-pipelinegit 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/migration-pipeline)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/migration-pipeline"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/migration-pipeline.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.03396 |
| Opus 5 | $0.00011 | $0.01698 |
| Sonnet 5 | $0.00004 | $0.00679 |
| Haiku 4.5 | $0.00002 | $0.00340 |
Grade A, and why
migration-pipeline 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 4d 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 — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migration Pipeline
Analyzed from commit:
412c71822on2026-05-04
Source: pkg/controller/plan/migration.go, pkg/controller/plan/kubevirt.go,
pkg/controller/plan/migrator/base/, pkg/controller/plan/migrator/ocp/
Migration.Run() — Top-Level Loop
The plan controller creates a Migration struct and calls Run() on each reconcile.
Run()
├── init() Build adapter (Client, Builder, Ensurer), KubeVirt helper,
│ Scheduler, and Migrator based on source provider type
├── begin() Mark migration started, ensure target namespace,
│ build VM status list and pipelines, call migrator.Begin()
├── resolveCanceledRefs()
├── for each runningVMs() → execute(vm) // Resume already-running VMs
├── loop: scheduler.Next() → execute(vm) // Schedule new VMs
└── end() Check all VMs completed → set Succeeded/Failed/Canceled
Polling: Run() returns PollReQ = 3s until all VMs complete, then NoReQ = 0.
Migrator Factory
migrator.New(context) in pkg/controller/plan/migrator/doc.go:
| Provider Type | Migrator | Notes |
|---|---|---|
openshift |
ocp.LiveMigrator |
Only for Plan.Spec.Type == MigrationLive |
openshift |
base.BaseMigrator |
For non-live OCP-to-OCP |
ec2 |
ec2migrator |
AWS EC2 custom migrator |
| All others | base.BaseMigrator |
vSphere, oVirt, OpenStack, OVA, HyperV |
Migrator Interface
Defined in pkg/controller/plan/migrator/base/doc.go:
type Migrator interface {
Init() error
Begin() error
Complete(*plan.VMStatus)
Status(plan.VM) *plan.VMStatus
Reset(*plan.VMStatus, []*plan.Step)
Itinerary(plan.VM) *libitr.Itinerary
Pipeline(plan.VM) ([]*plan.Step, error)
Step(*plan.VMStatus) string
ExecutePhase(*plan.VMStatus) (bool, error) // true = handled, false = delegate to migration.go
Logger() logging.LevelLogger
}
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.
- 4d ago First seen · 309 lines · 22 tokens per session scan A 455461bc1655
migration-pipeline is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 5d ago), licensed Apache-2.0. It adds 22 tokens to every session and 3,396 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
k8s
Kubernetes and Helm review and scaffolding for EKS workloads. Use when user says 'review my helm values', 'before I deploy', 'scaffold a new service', 'check values.yaml', or when working in values.yaml, Chart.yaml, or Helm template files.
kubernetes-helm
Kubernetes and Helm best practices including resource management, security, chart organization, and deployment patterns.
deployment
Rails Deployment with Kamal.
docker-deployment
Complete Docker containerization, production deployment, and monitoring patterns for POS System.
kubernetes
This rule provides comprehensive best practices for developing and maintaining Kubernetes applications and infrastructure, covering coding standards, security, performance, testing, and deployment.
fly-io
Cursor rule "fly-io" from jesseoue/cursor-rules, covering fly.toml, dockerfile, install dependencies only when needed, install dependencies based on the preferred package manager and rebuild the source code only when needed.