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/virt-v2vgit 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.00016 | $0.03753 |
| Opus 5 | $0.00008 | $0.01877 |
| Sonnet 5 | $0.00003 | $0.00751 |
| Haiku 4.5 | $0.00002 | $0.00375 |
Grade A, and why
virt-v2v 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 3d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
virt-v2v Integration
Analyzed from commit:
412c71822on2026-05-04
Overview
virt-v2v is the core guest conversion engine in Forklift. It runs as a pod during migration and is responsible for:
- Disk conversion — converting guest disk images from source format (VMDK, QCOW2, etc.) to raw format suitable for KubeVirt
- Guest OS inspection — detecting the OS type, distro, architecture via
virt-v2v-inspector - Driver injection — installing VirtIO drivers and removing source-specific drivers (e.g., VMware Tools)
- Guest customization — running
virt-customizescripts for network config, static IPs, and cleanup
Source: pkg/virt-v2v/ and cmd/virt-v2v/entrypoint.go
Entrypoint Flow (cmd/virt-v2v/entrypoint.go)
The virt-v2v pod entrypoint follows this sequence:
1. Load environment config (AppConfig)
2. Link SSL certificates (vSphere only)
3. Create output directory (/var/tmp/v2v)
4. Branch based on mode:
A. Remote Inspection (IsRemoteInspection=true):
└─ RunRemoteV2vInspection() → exits
B. Conversion (IsRemoteInspection=false):
├─ In-Place (IsInPlace=true):
│ ├─ With LibvirtUrl → GetDomainXML() → RunVirtV2vInPlace() (-i libvirtxml)
│ └─ Without LibvirtUrl → RunVirtV2vInPlaceDisk() (-i disk, e.g. EC2)
├─ Cold (default):
│ └─ RunVirtV2v() → pipes stdout to virt-v2v-monitor
│
├─ RunVirtV2VInspection() → local inspection on converted disks
├─ RunCustomize() → virt-customize with OS-specific scripts
│ (failure is non-fatal → adds Warning)
└─ Start HTTP server on :8080 (local migrations only)
Key behavior: customization failure does NOT fail the migration — it logs a warning exposed via /warnings.
Conversion Modes
Cold Migration (RunVirtV2v)
Used for vSphere, OVA, and HyperV. Runs virt-v2v with -o kubevirt output mode, producing KubeVirt YAML + converted disk images in the workdir.
Output is piped through virt-v2v-monitor which parses progress lines and exposes Prometheus metrics on :2112/metrics.
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.
- 3d ago First seen · 339 lines · 16 tokens per session scan A a9c32be883bc
virt-v2v is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 4d ago), licensed Apache-2.0. It adds 16 tokens to every session and 3,753 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
cursorrules
Robot control server. Do not move the physical robot without checking health first.
cursorrules
When the user asks about robotics control, use robotics-control-mcp tools: listdevices, sendcommand, readsensor, setservo, rungcode.
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.
cli-error-handling
CLI command error handling patterns.
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.