agentmods.dev

selectors

A coding rule for accessing properties of Kubernetes resources, such as pods, secrets, and custom resources. Kubernetes is a system for running and managing containerized applications.

In plain words
What is it for?
It is for reading names, namespaces, labels, annotations, API versions, kinds, provider settings, and other resource-specific values.
Why use it?
It replaces repeated direct property access with shared selector functions, keeping resource reads consistent and easier to maintain.

Cursor rule for Cursor

11 3d ago A scan 0 tokens original Apache-2.0
View the source file kubev2v/forklift-console-plugin
Install

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.

agentmods
npx agentmods add rules/kubev2v/forklift-console-plugin/selectors
Clone the repo
git clone --depth 1 https://github.com/kubev2v/forklift-console-plugin

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 397 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00397
Opus 5 $0.00000 $0.00198
Sonnet 5 $0.00000 $0.00079
Haiku 4.5 $0.00000 $0.00040

Measured 2d ago against content hash 969266bcb065, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

selectors 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.

.cursor/rules/selectors.mdc · 37 lines

What it actually says

Selector Usage Rule

When accessing properties of Kubernetes resources (CRDs, Pods, Secrets, etc.), always use a selector function instead of direct property chains.

Common selectors (@utils/crds/common/selectors)

Available for all K8sResourceCommon resources:

  • getName(resource) instead of resource?.metadata?.name
  • getNamespace(resource) instead of resource?.metadata?.namespace
  • getUID(resource) instead of resource?.metadata?.uid
  • getCreatedAt(resource) instead of resource?.metadata?.creationTimestamp
  • getLabels(resource) instead of resource?.metadata?.labels
  • getAnnotations(resource) instead of resource?.metadata?.annotations
  • getApiVersion(resource) instead of resource?.apiVersion
  • getKind(resource) instead of resource?.kind

Provider-specific:

  • getType(provider) instead of provider?.spec?.type
  • getProviderSecretRef(provider) instead of provider?.spec?.secret
  • getVddkInitImage(provider) instead of provider?.spec?.settings?.vddkInitImage

CRD-specific selectors

If a property access is specific to a CRD (e.g., Conversion, Plan), check for existing selectors under @utils/crds/<crd>/selectors.ts.

When no selector exists

  1. If the property is common to all K8s resources, add it to src/utils/crds/common/selectors.ts
  2. If the property is CRD-specific, add it to the CRD's selectors file under src/utils/crds/<crd>/selectors.ts
  3. Never access metadata.* or spec.* or status.* directly in component or hook code
Changes

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.

  1. 2d ago First seen · 37 lines · 0 tokens per session scan A 969266bcb065

Subscribe to this mod's changes

selectors is a cursor rule published in the GitHub repository kubev2v/forklift-console-plugin (11 stars, last pushed 3d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 397 tokens. 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.

ContainersDevOps and cloud
Related

Other cursor rules, from other repositories

aws-ecs

Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.

sanjeed5/awesome-cursor-rules-mdc · 2,640 tokens

backend

Backend development rules for TT Studio - AI model management backend.

tenstorrent/tt-studio · 0 tokens

development

Development environment setup and commands for backend services.

kivo360/OmoiOS · 0 tokens

devops-infrastructure

DevOps and infrastructure: Docker, Kubernetes, Terraform, CI/CD. Load when editing Dockerfiles, compose, k8s manifests, Terraform, or workflow YAML — not for application code.

madebyaris/advance-minimax-m3-cursor-rules · 0 tokens

docker-database

Docker configuration for PostgreSQL database and Elasticsearch.

proyecto26/projectx · 0 tokens

hack

Hack v3 is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.

hack-dance/hack · 2,144 tokens