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-railguard-available)<a href="https://agentmods.dev/rules/brighton-labs/railguard-cursor-coding/terraform-secure-railguard-available"><img src="https://agentmods.dev/badge/rules/brighton-labs/railguard-cursor-coding/terraform-secure-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-railguard-available"><img src="https://agentmods.dev/badge/rules/brighton-labs/railguard-cursor-coding/terraform-secure-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.01162 | $0.01162 |
| Opus 5.5 | $0.00465 | $0.00465 |
| Sonnet 5.5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
terraform-secure-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 2mo 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.
Overview
This rule provides secure-by-default conventions for Terraform projects, focused on:
- Multi-environment infrastructure deployment (e.g., dev, staging, prod)
- Separation of concerns through modular component structure
- Validation of all input and deployed resources
- Secure secret handling and backend configuration
- Encryption of data at rest and in transit
- Principle of least privilege for all IAM interactions
Note: Input validation logic is delegated to:
.cursor/rules/railguard-input-validation.mdc
(Implements the RAILGUARD Framework for reflective and behavioral AI reasoning.)
Code Validation and Resource Governance
- Validate all external code and modules before use. Trust must be established for source and content.
- Always use HTTPS or SSH for module sources — avoid unsecured sources.
- Inputs must be declared in a dedicated
.tffile, typed, and validated. - Add extra validation logic if input trust is unclear or incomplete.
- Avoid generation of high-cost resources unless explicitly scoped to critical workloads.
- Version pin all providers and modules (
~>,>=, avoidlatest). - All code must pass static scanning tools like
tfsec,Checkov, orTerrascan. - Annotate outputs or critical code with security comments (e.g.,
# encrypted,# least privilege).
Input Validation
All input validation (schema, type, behavioral assumptions) is enforced globally via:
.cursor/rules/railguard-input-validation.mdc
This includes:
- Dangerous input detection
- Variable schema enforcement
- Secure interpretation and reasoning scaffolding
Secrets and Sensitive Data
- All API keys, tokens, and credentials must be stored in Vaults or environment variables.
- Do not hardcode sensitive values or place them in
.tfvarsor Terraform files. - Mark sensitive outputs using
sensitive = true. - Terraform state must be stored in secure, encrypted remote backends (e.g., S3 + DynamoDB, GCS).
- Add
.gitignorerules to exclude sensitive config or.tfstatefiles locally. - Use secure hashing algorithms for secret comparison or ID generation.
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.
- 2mo ago First seen · 152 lines · 1,162 tokens per session scan A dbf66c0675aa
terraform-secure-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 1,162 tokens to every session, about $0.0046 per session on Opus 5.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
log-watch
Set up a scheduled agent that reads a small team's existing production logs, flags suspicious activity, and pages a human, without a SIEM or security staff. Use when the user mentions 'log watch,' 'watch my logs,' 'alert me if someone is attacking,' 'no SIEM,' 'poor man's SIEM,' 'agent reads CloudTrail,' 'cron job…
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
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.