awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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/sanjeed5/awesome-cursor-rules-mdc/kubernetesgit clone --depth 1 https://github.com/sanjeed5/awesome-cursor-rules-mdcWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/kubernetes)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/kubernetes"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/kubernetes.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02943 | $0.02943 |
| Opus 5 | $0.01471 | $0.01471 |
| Sonnet 5 | $0.00589 | $0.00589 |
| Haiku 4.5 | $0.00294 | $0.00294 |
Grade A, and why
kubernetes 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 — 500 lines — stays where its author put it; the contents beside it link to each section on GitHub.
kubernetes Best Practices
Kubernetes manifests are your application's blueprint. Treat them as code. These rules ensure your deployments are secure, stable, and easy to manage.
Code Organization and Structure
Organize your Kubernetes manifests for clarity and maintainability. Avoid monolithic files.
1. One Resource Per File (or Logical Group)
Keep files focused. Group related resources (e.g., Deployment, Service, HPA for a single microservice) into a dedicated directory, but separate individual resource types into their own files within that directory.
❌ BAD: Monolithic file for an entire application.
# app.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-app-deployment
spec:
# ...
---
apiVersion: v1
kind: Service
metadata:
name: my-app-service
spec:
# ...
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: my-app-ingress
spec:
# ...
✅ GOOD: Separate files for each resource type, grouped by application.
# Directory structure
my-app/
├── deployment.yaml
├── service.yaml
└── ingress.yaml
# my-app/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: my-app-deployment
labels:
app: my-app
spec:
selector:
matchLabels:
app: my-app
template:
metadata:
labels:
app: my-app
spec:
containers:
- name: my-app
image: myregistry/my-app:v1.2.3
ports:
- containerPort: 8080
2. Consistent Labeling Strategy
Labels are critical for selection, organization, and automation. Use a consistent set of labels across all resources.
✅ GOOD: Standardized labels for app, tier, environment, version.
apiVersion: apps/v1
kind: Deployment
metadata:
name: auth-service
labels:
app.kubernetes.io/name: auth-service
app.kubernetes.io/instance: auth-service-prod
app.kubernetes.io/version: "1.0.0"
app.kubernetes.io/component: backend
app.kubernetes.io/part-of: my-application
app.kubernetes.io/managed-by: kustomize
spec:
selector:
matchLabels:
app.kubernetes.io/name: auth-service
app.kubernetes.io/instance: auth-service-prod
template:
metadata:
labels:
app.kubernetes.io/name: auth-service
app.kubernetes.io/instance: auth-service-prod
# ...
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 · 500 lines · 2,943 tokens per session scan A 2efb4b1a294c
kubernetes is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 2,943 tokens to every session, about $0.0147 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-09-03.
Other cursor rules, from other repositories
kubernetes
Kubernetes and OpenShift workload generation rules — security defaults, resource limits, probes.
build-deployment
Build, CMake, and Docker deployment.
kubernetes-helm
Kubernetes and Helm best practices including resource management, security, chart organization, and deployment patterns.
deployment
Rails Deployment with Kamal.
004_Dynamo_Distributed_Deployment_Kubernetes
NVIDIA Dynamo Distributed Deployment on Kubernetes - Production-ready orchestration with Helm, operators, and multi-node scaling.
fly-io
Cursor rule "fly-io" from jesseoue/cursor-rules, covering fly.toml, dockerfile, install dependencies only when needed, install dependencies based on the preferred package manager and rebuild the source code only when needed.