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/plansgit 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.03898 |
| Opus 5 | $0.00008 | $0.01949 |
| Sonnet 5 | $0.00003 | $0.00780 |
| Haiku 4.5 | $0.00002 | $0.00390 |
Grade A, and why
plans 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 2d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Pages
Analyzed on 2026-05-29 — ~240
.tsxfiles, the largest feature in the plugin.
Plugin Registration (dynamic-plugin.ts)
Exposes three modules to the Console SDK:
| Extension type | Module | Component |
|---|---|---|
console.navigation/resource-ns |
— | Nav items (admin + virt perspectives) |
console.page/resource/list |
PlansListPage |
PlansListPage |
console.page/resource/details |
PlanDetailsNav |
PlanDetailsNav |
console.resource/create |
PlanCreatePage |
PlanCreatePage |
All use PlanModelGroupVersionKind from @forklift-ui/types.
Page Composition
1. List Page — PlansListPage
PlansListPage
├── LearningExperienceDrawer
└── StandardPage ← shared, data-driven table
├── PlansAddButton ← gated by useGetDeleteAndEditAccessReview
├── PlansEmptyState
└── PlanRow (per row)
└── usePlanListRowFields ← renders each column cell
Data source: useK8sWatchResource<V1beta1Plan[]> (list, namespaced).
Table columns (defined in planFields): Name, Project, Source provider, Target project, Virtual machines count, Migration status, Migration type, Migration started, Description, Actions. Plus a hidden "Archived" slider filter.
Post-filter: Archived plans are hidden by default; toggling the "Show archived" slider includes them.
2. Create Page — PlanCreatePage → CreatePlanWizard
PlanCreatePage
├── LearningExperienceDrawer
├── Title ("Create migration plan")
└── CreatePlanWizard
├── FormProvider (react-hook-form)
├── CreatePlanWizardContextProvider
└── CreatePlanWizardInner ← PF6 Wizard shell
├── WizardStep (Basic setup) ← expandable parent
│ ├── GeneralInformationStep
│ ├── VirtualMachinesStep
│ ├── NetworkMapStep
│ ├── StorageMapStep
│ └── MigrationTypeStep ← conditionally hidden
├── WizardStep (Additional setup) ← expandable parent
│ ├── OtherSettingsStep
│ ├── CustomScriptsStep
│ └── HooksStep
└── WizardStep (Review and create)
└── ReviewStep
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.
- 2d ago First seen · 310 lines · 16 tokens per session scan A d919c2791f45
plans 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 16 tokens to every session and 3,898 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
wize-sprint-status
4-implementation: Sprint Status.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
operating-model
Engineering operating model — workflow, risk classification, scope discipline.
sprint-planning
BMAD BMM Agent: sprint-planning.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.