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/provider-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.00014 | $0.02852 |
| Opus 5 | $0.00007 | $0.01426 |
| Sonnet 5 | $0.00003 | $0.00570 |
| Haiku 4.5 | $0.00001 | $0.00285 |
Grade A, and why
provider-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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Provider Controller (Common)
Analyzed from commit:
412c71822on2026-05-04
Source: pkg/controller/provider/ in the forklift backend.
Reconciliation Loop
The Provider controller watches Provider, Secret, OVAProviderServer, and HyperVProviderServer resources. On each reconcile cycle it runs the following steps in order:
Reconcile(request)
│
├─ 1. Fetch Provider CR (delete container if NotFound)
├─ 2. Set phase = Staging, begin staging conditions
├─ 3. Provider-server lifecycle (OVA / HyperV only)
│ ├─ If deletion → cleanupProviderServer (remove server + finalizer)
│ └─ If alive → ensureProviderServer (create/redeploy)
├─ 4. Validate
│ ├─ validateType
│ ├─ validateURL
│ ├─ validateSecret (provider-type-specific key checks)
│ ├─ testConnection (builds ephemeral collector, calls Test())
│ ├─ inventoryCreated (checks collector parity)
│ ├─ validateSSHReadiness (vSphere + SSH method only)
│ └─ validateSMBCSI (HyperV only)
├─ 5. Ensure SSH keys (vSphere only)
├─ 6. Update container (build/replace inventory collector)
├─ 7. Ready check
│ └─ If no blocker AND ConnectionTestSucceeded + InventoryCreated → phase = Ready
├─ 8. Update DB (sync provider into collector owner)
├─ 9. Requeue
│ ├─ SlowReQ if not yet ConnectionTestSucceeded + InventoryCreated
│ └─ LongReQ for periodic re-testing
│
└─ deferred: EndStagingConditions → updateProviderStatus
Stop reconciliation entirely on ConnectionAuthFailed
Key behaviors
- Generation tracking:
HasReconciled()comparesObservedGenerationwithGeneration. When the provider spec changes, the old collector is shut down and its DB closed before a new one is created. - Secret change detection:
SecretResourceVersionin status tracks the last reconciled secret version. When it changes the collector is replaced even if the provider spec hasn't changed. - Auth failure stops reconciliation: If
ConnectionAuthFailedis set,RequeueAfteris zeroed and no further reconciles happen until the secret/spec changes (prevents account lockout).
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 · 251 lines · 14 tokens per session scan A 33f946d7b94a
provider-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 14 tokens to every session and 2,852 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.