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/shared-librariesgit 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.03419 |
| Opus 5 | $0.00008 | $0.01709 |
| Sonnet 5 | $0.00003 | $0.00684 |
| Haiku 4.5 | $0.00002 | $0.00342 |
Grade A, and why
shared-libraries 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 — 400 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Shared Libraries (pkg/lib)
Analyzed from commit:
412c71822on2026-05-04
All Forklift controllers share a common set of library packages under pkg/lib/. Understanding these is essential because they define the patterns every controller follows.
1. Condition Framework (pkg/lib/condition) — CRITICAL
The condition framework is the core abstraction for resource status. Every CRD's .status.conditions field uses it.
1.1 Condition Struct
type Condition struct {
Type string // e.g. "Ready", "ReconcileFailed", "ConnectionTestFailed"
Status string // "True" or "False"
Category string // severity: Critical, Error, Warn, Required, Advisory
Reason string // machine-readable reason
Message string // human-readable description
Suggestion string // suggested resolution
LastTransitionTime Time // when status last changed
Durable bool // if true, survives staging sweeps
Items []string // referenced items in Message
staged bool // internal: was this set in current cycle?
}
1.2 Categories (Severity Levels)
| Category | Constant | Effect |
|---|---|---|
Critical |
Blocks Reconcile() AND blocks Ready |
|
Error |
Blocks Ready only |
|
Warn |
Does NOT block Ready — advisory warning |
|
Required |
Required for Ready to be true |
|
Advisory |
Purely informational |
Special categories for pending states: ValidatingVDDK, VMMissingGuestIPs, VMMissingChangedBlockTracking, SharedDisks.
1.3 Conditions Collection — The Staging Pattern
Conditions is a managed slice embedded in every resource's Status:
type Conditions struct {
List []Condition // serialized to JSON
staging bool // internal staging state
}
The staging lifecycle (used in every controller's Reconcile):
// 1. Begin staging — marks all non-Durable conditions as un-staged
resource.Status.BeginStagingConditions()
// 2. Set conditions for current reconcile cycle
// Each SetCondition call marks that condition as staged
resource.Status.SetCondition(Condition{
Type: "SomeValidation",
Status: True,
Category: Error,
Message: "Something is wrong",
})
// 3. End staging — deletes any conditions NOT set/staged this cycle
// Durable conditions always survive
resource.Status.EndStagingConditions()
// 4. Derive the Ready condition from blocker status
resource.Status.SetCondition(Condition{
Type: Ready,
Status: boolToStatus(!resource.Status.HasBlockerCondition()),
Category: Required,
Message: "Resource is ready.",
})
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 · 400 lines · 16 tokens per session scan A 5d620f30e967
shared-libraries 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 16 tokens to every session and 3,419 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.