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.
git clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/nitinjain999/platform-skills/kubernetes)<a href="https://agentmods.dev/rules/nitinjain999/platform-skills/kubernetes"><img src="https://agentmods.dev/badge/rules/nitinjain999/platform-skills/kubernetes/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/nitinjain999/platform-skills/kubernetes"><img src="https://agentmods.dev/badge/rules/nitinjain999/platform-skills/kubernetes.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00790 |
| Opus 5.5 | $0.00000 | $0.00316 |
| Sonnet 5.5 | $0.00000 | $0.00158 |
| Haiku 4.5 | $0.00000 | $0.00079 |
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 9d 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes & OpenShift Rules
Always generate Deployments with all of the following. Missing any item is a Critical finding.
Required fields on every container
resources:
requests:
cpu: "100m"
memory: "128Mi"
limits:
memory: "256Mi" # Set memory limit. Omit cpu limit — it causes throttling.
securityContext:
runAsNonRoot: true
runAsUser: 1000 # Omit on OpenShift — SCC assigns the UID
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities:
drop: ["ALL"]
livenessProbe:
httpGet: { path: /healthz, port: 8080 }
initialDelaySeconds: 10
periodSeconds: 10
readinessProbe:
httpGet: { path: /ready, port: 8080 }
initialDelaySeconds: 5
periodSeconds: 5
Required ServiceAccount settings
automountServiceAccountToken: false
Required pod-level securityContext
spec:
securityContext:
seccompProfile:
type: RuntimeDefault
Ingress
Never propose ingress-nginx for new work: its best-effort maintenance ended in March 2026 (no releases, bug fixes or security fixes). Default to Gateway API with Envoy Gateway.
- One shared
Gatewayowned by the platform team; app teams ownHTTPRoutes in their own namespaces - Bind each HTTPS listener to the namespace that owns its hostname (
allowedRoutesselector onkubernetes.io/metadata.name); neverfrom: All, never one shared opt-in label - Gateway API CRDs on the standard channel, applied as plain manifests, never a Helm release (too large for its 1 MiB Secret), and never garbage-collected: Flux
prune: false+deletionPolicy: Orphan(deleting a CRD deletes every Gateway and route). Envoy Gateway's controller chart bundles experimental CRDs: setcrds.enabled: false - App namespaces belong to the platform layer, not the app layer
- TLS via cert-manager v1.15+ with
config.gatewayAPI.enabled: true; one HTTPS listener per hostname withhostname,tls.mode: Terminate,certificateRefs - Flux:
infrastructure(CRDs, controllers) →infrastructure-configs(Gateway objects) →apps(routes), with ahealthCheckExprscheck on GatewayProgrammed - Port-80 HTTPS redirect with
statusCode: 308;backendRefsuse the Service port number - Migrating: inventory annotations first; treat every ingress2gateway warning as blocking; run both controllers in parallel and move traffic by DNS one hostname at a time; decommission ingress-nginx in a separate change after a soak
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.
- 9d ago Changed · +14 lines 040406b6f6b8
- 1mo ago First seen · 62 lines · 0 tokens per session scan A 9d74fc8fd9b5
kubernetes is a cursor rule published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 790 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.
Other cursor rules, from other repositories
kubernetes
This rule provides comprehensive best practices for developing and maintaining Kubernetes applications and infrastructure, covering coding standards, security, performance, testing, and deployment.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.