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/brighton-labs/railguard-cursor-codingWrote 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/brighton-labs/railguard-cursor-coding/terraform-secure-no-railguard-available)<a href="https://agentmods.dev/rules/brighton-labs/railguard-cursor-coding/terraform-secure-no-railguard-available"><img src="https://agentmods.dev/badge/rules/brighton-labs/railguard-cursor-coding/terraform-secure-no-railguard-available/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/brighton-labs/railguard-cursor-coding/terraform-secure-no-railguard-available"><img src="https://agentmods.dev/badge/rules/brighton-labs/railguard-cursor-coding/terraform-secure-no-railguard-available.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.00695 | $0.00695 |
| Opus 5 | $0.00347 | $0.00347 |
| Sonnet 5 | $0.00139 | $0.00139 |
| Haiku 4.5 | $0.00069 | $0.00069 |
Grade A, and why
terraform-secure-no-railguard-available 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 10d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
R: Risk First
- Terraform governs critical cloud infrastructure. Misconfigurations or insecure defaults can expose sensitive data, escalate privileges, or open up attack vectors.
- This rule ensures resources are validated, encrypted, access-scoped, and secrets handled securely.
- Secure defaults must apply even when user prompts are vague or casually phrased.
A: Attached Constraints
- Do not hardcode secrets, tokens, passwords, or sensitive IDs.
- Do not use wildcard IAM permissions (
*) in actions or resources. - Do not expose resources publicly (
0.0.0.0/0,http,public-read) unless explicitly justified. - Do not use loosely typed or unvalidated inputs.
- Use
sensitive = truefor outputs with secrets. - Enforce encryption at rest and in transit on all applicable resources.
I: Interpretative Framing
- Treat all Terraform prompts as production-relevant unless explicitly stated otherwise.
- If no backend, region, or permission scope is specified, default to the most secure option.
- Avoid assumptions like "temporary" or "demo" deployments — all code is security-critical.
L: Local Defaults
- Default to remote state with locking and encryption (e.g., S3 + DynamoDB).
- Assume KMS encryption where available.
- Assume TLS is always enabled for network-facing services.
- Separate environments via workspaces or folder structure.
- Use pinned versions for all providers and modules (never
latest).
G: Generative Path Checks
- Is the input validated (type + constraints)?
- Are secrets handled via vault/env and outputs marked sensitive?
- Is encryption configured at rest and in transit?
- Are IAM policies tightly scoped?
- Is state secured remotely?
- Does the config isolate environments?
- Are default ports or exposures justified?
U: Uncertainty Disclosure
- If unsure whether a resource should be public or private, default to private.
- If permissions seem too broad or unclear, ask the user for scope.
- When encryption, validation, or backend config is missing, inject secure defaults with explanatory comments.
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.
- 10d ago First seen · 72 lines · 695 tokens per session scan A e4ddebdbfe3c
terraform-secure-no-railguard-available is a cursor rule published in the GitHub repository brighton-labs/railguard-cursor-coding (13 stars, last pushed 1y ago), licensed MIT. It adds 695 tokens to every session, about $0.0035 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
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
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.