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/ovagit 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/ova)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/ova"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/ova.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.00023 | $0.02146 |
| Opus 5 | $0.00012 | $0.01073 |
| Sonnet 5 | $0.00005 | $0.00429 |
| Haiku 4.5 | $0.00002 | $0.00215 |
Grade A, and why
ova 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OVA Provider
Analyzed from commit:
412c71822on2026-05-04
Architecture Overview
The OVA provider imports VMs from OVF/OVA files stored on an NFS share. It uses a sidecar server pattern: a dedicated pod (OVA provider server) mounts the NFS share, parses OVF descriptors, and exposes a REST API. The main inventory controller then polls this sidecar to build its in-memory DB.
NFS Share (OVA/OVF files)
│
▼
┌─────────────────────────┐
│ OVA Provider Server │ (Deployment + Service in Forklift namespace)
│ - Mounts NFS via PV │
│ - Parses OVF files │
│ - Exposes REST :8080 │
└────────────┬────────────┘
│ HTTP (cluster-internal)
▼
┌─────────────────────────┐
│ Inventory Collector │ (runs inside forklift-controller)
│ - Polls sidecar API │
│ - Stores in libmodel DB│
│ - Validates VMs (OPA) │
└────────────┬────────────┘
│
▼
┌─────────────────────────┐
│ Inventory REST API │ (gin handlers in forklift-controller)
│ /providers/ova/:uid/… │
└─────────────────────────┘
Key Source Locations
| Component | Path (under pkg/) |
|---|---|
| Collector (thin wrapper) | controller/provider/container/ova/collector.go |
| Shared OVF collector logic | controller/provider/container/ovfbase/ |
| OVF data model | controller/provider/model/ovf/ |
| REST API handlers | controller/provider/web/ova/ + web/ovfbase/ |
| OVAProviderServer controller | controller/ova/ |
OVAProviderServer CRD
Kind: OVAProviderServer (group forklift.konveyor.io/v1beta1)
Finalizer: api.OvaProviderFinalizer
Controller name: ova-server
Lifecycle
- Provider controller creates an
OVAProviderServerCR when an OVA-type Provider is reconciled. - The OVA server controller watches
OVAProviderServerand ensures these resources:- PersistentVolume — NFS volume,
ReadOnlyMany, source parsed fromProvider.Spec.URL(server:pathformat). - PersistentVolumeClaim — Binds to the PV, owned by the OVAProviderServer.
- Deployment — Runs the sidecar image (
Settings.Providers.OVA.ContainerImage), mounts NFS at/ova. - Service — ClusterIP on port
8080, namedapi-http.
- PersistentVolume — NFS volume,
- On deletion, the controller tears down Service → Deployment → PVC → PV.
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 · 256 lines · 23 tokens per session scan A 7cb41be46f93
ova 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 23 tokens to every session and 2,146 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
tf-plan
Review a Terraform plan before applying it: destroys and replacements of data-bearing resources, secrets readable in plan output, out-of-band drift, blast radius, and whether the apply is bound to the plan you actually reviewed. Use when user says 'review my plan', 'is this plan safe to apply', 'check tfplan', 'what…
netlify-tanstack-deploy
Netlify + TanStack Start — netlify.toml at repo root with [build] base; MISSION CRITICAL — dashboard Build settings (Base, Publish, Build command, Functions directory, etc.) must stay empty or deploys break.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
aws-resource-naming
AWS resource naming and tagging conventions for SilverKey infrastructure changes.
kubernetes-helm
Kubernetes and Helm best practices including resource management, security, chart organization, and deployment patterns.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.