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/plan-controllergit 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.02889 |
| Opus 5 | $0.00006 | $0.01444 |
| Sonnet 5 | $0.00003 | $0.00578 |
| Haiku 4.5 | $0.00001 | $0.00289 |
Grade A, and why
plan-controller 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 — 284 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Controller
Analyzed from commit:
412c71822on2026-05-04
Overview
The Plan controller (pkg/controller/plan/controller.go) is the central reconciler for migration plans. It watches Plan CRs plus related resources (Provider, NetworkMap, StorageMap, Hook, Migration) and drives the full lifecycle from validation through execution.
The Migration controller (pkg/controller/migration/controller.go) is intentionally thin — it sets owner references, validates the plan reference, and reflects plan snapshot status back onto the Migration CR.
Reconcile Flow
Reconcile(plan)
│
├─ 1. Fetch Plan (abort if deleted → cleanup orphaned resources)
├─ 2. Skip if Archived (spec.archived + status has Archived condition)
├─ 3. Skip if Succeeded (unless needs archiving)
├─ 4. Postpone if dependencies not yet reconciled
│ (Provider, NetworkMap, StorageMap, Host, Hook ObservedGeneration < Generation)
├─ 5. BeginStagingConditions()
├─ 6. validate(plan) — sets conditions on plan.Status
│ └─ If validation returns error for dangling archived plan → archive + return
├─ 7. Set PopulatorDataSource labels (one-time, post-Succeeded/Failed/Canceled)
├─ 8. Archive if spec.archived
├─ 9. Set Ready condition (if no blockers, not archived, not validating VDDK)
├─ 10. EndStagingConditions()
└─ 11. execute(plan) — find/run migration, update status
Execute Flow
execute(plan)
│
├─ If blocker/archived/reQ-condition → fail executing migration if grace period exceeded → return
├─ Build plancontext.Context
├─ Find active migration (from snapshot)
│ ├─ If found → SetMigration, matchSnapshot (cancel if mutated)
│ └─ If snapshot marked Canceled → propagate to all non-terminal VMs
├─ runner.Cancel() — cancel VMs marked for cancellation
├─ Find pending migrations (sorted by creationTimestamp)
├─ If no active + pending exists → select first pending, create new snapshot
├─ If no migration at all → delete Executing condition, slow requeue
├─ runner.Run() — execute the migration
└─ Reflect snapshot conditions (Executing/Succeeded/Failed/Canceled) onto plan.Status
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 · 284 lines · 13 tokens per session scan A 10cfcd3f208d
plan-controller is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 2d ago), licensed Apache-2.0. It adds 13 tokens to every session and 2,889 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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.