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/gracefullight/docusaurus-pluginsWrote 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/gracefullight/docusaurus-plugins/infrastructure)<a href="https://agentmods.dev/rules/gracefullight/docusaurus-plugins/infrastructure"><img src="https://agentmods.dev/badge/rules/gracefullight/docusaurus-plugins/infrastructure/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/gracefullight/docusaurus-plugins/infrastructure"><img src="https://agentmods.dev/badge/rules/gracefullight/docusaurus-plugins/infrastructure.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.00397 |
| Opus 5.5 | $0.00000 | $0.00159 |
| Sonnet 5.5 | $0.00000 | $0.00079 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
infrastructure 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 1mo 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.
This is a copy
100% identical to infrastructure — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Infrastructure Standards
Core Rules
- Provider-Agnostic: Detect cloud provider from project context before writing any HCL
- Remote State: Store state in remote backend (S3, GCS, Azure Blob) with versioning and locking
- OIDC First: Use OIDC/IAM roles for CI/CD authentication instead of long-lived credentials
- Plan Before Apply: Always run
terraform validate,terraform fmt,terraform planbefore apply - Least Privilege: IAM policies must follow least privilege; never use overly permissive policies
- Tag Everything: Apply Environment, Project, Owner, CostCenter tags/labels to all taggable resources
- No Secrets in Code: Never hardcode passwords, API keys, or tokens in .tf files
- Composable Modules: Design reusable modules with clear interfaces; avoid monolithic modules
- Environment Sizing: Use environment-based sizing (smaller for dev/staging, production-grade for prod)
- Policy as Code: Run OPA/Sentinel and security scanning (Checkov, tfsec) in CI/CD before apply
- Version Pinning: Pin all providers and modules; use
for_eachovercount - Cost Awareness: Implement lifecycle policies, autoscaling schedules, and review cost estimates before apply
- No Auto-Approve: Never use
auto-approvein production; neverterraform destroywithout backup - Drift Detection: Never skip drift detection in production
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.
- 1mo ago First seen · 27 lines · 0 tokens per session scan A ad9c0a0a9ae1
infrastructure is a cursor rule published in the GitHub repository gracefullight/docusaurus-plugins (23 stars, last pushed 24d ago), licensed MIT. 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. It is 100% identical to infrastructure, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
working-with-operator
when the user is modifying the Kubernetes operator, CRDs, or controller logic.
viberaven-deploy
Apply before changing Vercel config or deploy CI workflows.
platform-engineer
Cursor rule "platform-engineer" from ulises-jeremias/agent-toolkit, covering platform engineer, responsibility, main skill domains, when invoked and delegate to skills.
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.