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/ec2)<a href="https://agentmods.dev/rules/kubev2v/forklift-console-plugin/ec2"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/ec2/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/ec2"><img src="https://agentmods.dev/badge/rules/kubev2v/forklift-console-plugin/ec2.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.00017 | $0.03569 |
| Opus 5.5 | $0.00007 | $0.01428 |
| Sonnet 5.5 | $0.00003 | $0.00714 |
| Haiku 4.5 | $0.00002 | $0.00357 |
Grade A, and why
ec2 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EC2 Provider
Analyzed from commit:
baf9c7bccon2026-09-17Source paths:pkg/provider/ec2/
Package Purpose
The EC2 provider migrates Amazon EC2 instances to OpenShift Virtualization using cold migration only. Unlike other Forklift providers (under pkg/controller/provider/), EC2 lives in a self-contained tree at pkg/provider/ec2/ with its own inventory collector, REST API, plan adapter, migrator, builder, validator, ensurer, scheduler, and AWS clients.
Migration flow: stopped EC2 instance → EBS snapshots → (optional cross-account snapshot sharing) → EBS volumes in target AZ → PV/PVC pairs via AWS EBS CSI (ebs.csi.aws.com) → optional virt-v2v guest conversion → KubeVirt VM. AWS resource state is tracked via forklift.konveyor.io/* tags (not Kubernetes), making phases idempotent across controller restarts.
pkg/provider/ec2/
├── controller/ # Plan integration (adapter, migrator, builder, …)
│ ├── adapter/ # base.Adapter factory
│ ├── builder/ # VirtualMachine + PV/PVC spec generation
│ ├── client/ # AWS SDK (power, snapshots, volumes)
│ ├── ensurer/ # K8s resource creation (PV, PVC)
│ ├── handler/ # Plan reconciliation event handlers
│ ├── inventory/ # Inventory lookup helpers
│ ├── mapping/ # Network/storage mapping utilities
│ ├── migrator/ # Migration state machine
│ ├── scheduler/ # MaxInFlight VM scheduling
│ ├── validation/ # Provider CR validation (target credentials)
│ └── validator/ # Pre-migration VM validation
├── inventory/ # Inventory collection and REST API
│ ├── client/ # AWS SDK client for polling
│ ├── collector/ # Periodic AWS API poller
│ ├── model/ # SQLite DB models
│ └── web/ # REST handlers (gin)
├── testutil/ # Fake EC2/STS APIs
└── docs/ # Tagging, guest conversion, feature comparison
Key Types and Structs
Inventory models (inventory/model/)
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 · +22 lines 91164b642e76
- 1mo ago First seen · 295 lines · 17 tokens per session scan A b84805426774
ec2 is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 3,569 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
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
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.