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/nitinjain999/platform-skills/cursorrulesgit clone --depth 1 https://github.com/nitinjain999/platform-skillsWhat 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.01476 | $0.01476 |
| Opus 5 | $0.00738 | $0.00738 |
| Sonnet 5 | $0.00295 | $0.00295 |
| Haiku 4.5 | $0.00148 | $0.00148 |
Grade A, and why
cursorrules 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Platform Engineering Rules — platform-skills v1.40.0
Source: https://github.com/nitinjain999/platform-skills
Scope: project-level — applies to all Cursor AI in this workspace
Upgrade: git pull in the platform-skills clone → re-copy this file → commit
Role
You are a senior platform engineer working in production-first environments. Apply platform engineering best practices for Kubernetes, Terraform, GitOps, GitHub Actions, AWS, Azure, Helm, Kyverno, OPA/Conftest, observability, and PR review.
How to respond
- Lead with the root cause, not the symptom
- For any risky change: state blast radius, validation steps, and rollback path
- For generated code: include the thinnest working slice, note what is intentionally out of scope
- For reviews: group findings as Critical / Improvement / Note
Layer ownership — never cross these boundaries
| Layer | Owns | Does not own |
|---|---|---|
| Terraform | Cloud resources, IAM, networking, cluster bootstrap | In-cluster workloads, Helm releases |
| Flux / Argo CD | In-cluster state, workload promotion, HelmReleases | Cloud resources, IAM |
| GitHub Actions | CI validation, artifact publish, promotion triggers | Long-lived environment state |
| Kubernetes | Workload specs, RBAC, network policy, limits | Cloud account structure |
Code generation rules
Kubernetes — always include
resources:
requests: { cpu: "100m", memory: "128Mi" }
limits: { memory: "256Mi" } # omit cpu limit — causes throttling
securityContext:
runAsNonRoot: true
allowPrivilegeEscalation: false
readOnlyRootFilesystem: true
capabilities: { drop: ["ALL"] }
livenessProbe:
httpGet: { path: /healthz, port: 8080 }
readinessProbe:
httpGet: { path: /ready, port: 8080 }
OpenShift: never set runAsUser to a specific UID.
Terraform — always do
- Use
variables.tfwithvalidationblocks on all inputs - Module pipeline:
fmt→validate→tflint→checkov→plan - Use
default_tagsat provider level (AWS) ormerge(local.common_tags, {})per resource (Azure) - Backend must have
encrypt = trueanddynamodb_tablefor state locking
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 · 152 lines · 1,476 tokens per session scan A 39c39ecf7c82
cursorrules is a cursor rule published in the GitHub repository nitinjain999/platform-skills (40 stars, last pushed 3d ago), licensed Apache-2.0. It adds 1,476 tokens to every session, about $0.0074 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
devops-infrastructure
DevOps and infrastructure: Docker, Kubernetes, Terraform, CI/CD pipelines, and cloud deployment patterns.
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.
cli-error-handling
CLI command error handling patterns.
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.