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/schedulergit 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.00013 | $0.02095 |
| Opus 5 | $0.00006 | $0.01047 |
| Sonnet 5 | $0.00003 | $0.00419 |
| Haiku 4.5 | $0.00001 | $0.00210 |
Grade A, and why
scheduler 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 — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Scheduler
Analyzed from commit:
412c71822on2026-05-04
Overview
The scheduler determines which VM to migrate next from a Plan's VM list. It enforces concurrency limits to prevent overloading source infrastructure. Each provider type has its own scheduler implementation, but all share the same interface and factory.
Source: pkg/controller/plan/scheduler/
Scheduler Interface
// pkg/controller/plan/scheduler/doc.go
type Scheduler interface {
Next() (vm *plan.VMStatus, hasNext bool, err error)
}
Next() returns:
vm— the nextVMStatuseligible to start migrationhasNext—trueif a VM was found,falseif all are busy/done or concurrency limit reachederr— any error during scheduling
Factory
scheduler.New(ctx *plancontext.Context) creates the correct scheduler based on ctx.Source.Provider.Type(). All schedulers receive settings.Settings.MaxInFlight as their concurrency limit.
MaxInFlight Setting
| Setting | Env Var | Default | Scope |
|---|---|---|---|
MaxInFlight |
MAX_VM_INFLIGHT |
20 | Per source provider (all plans sharing the same provider) |
Defined in pkg/settings/migration.go. Must be a positive integer.
Two Scheduling Models
1. Simple Model (oVirt, OpenStack, OCP, OVA, Hyper-V, EC2)
These providers use a flat VM-count concurrency model:
inFlight (running VMs across all plans for same provider) < MaxInFlight → schedule next VM
Algorithm (Next()):
- Acquire package-level mutex
- List all Plans in the cluster
- Count running VMs across all Plans sharing the same source provider (skip archived, non-executing plans)
- If
inFlight >= MaxInFlight→ return no VM - Iterate this Plan's VMs in order; return the first VM that is not canceled, not started, and not completed
Concurrency unit: 1 VM = 1 slot. Simple counter across the provider.
2. Host-Aware Model (vSphere only)
vSphere uses a per-ESXi-host disk-count concurrency model. The limit is per host, not globally flat:
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 · 217 lines · 13 tokens per session scan A dd2b3392b075
scheduler is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 3d ago), licensed Apache-2.0. It adds 13 tokens to every session and 2,095 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
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.