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/pallerana/agentic-loop-engineering-kitWrote 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/pallerana/agentic-loop-engineering-kit/terraform-standards)<a href="https://agentmods.dev/rules/pallerana/agentic-loop-engineering-kit/terraform-standards"><img src="https://agentmods.dev/badge/rules/pallerana/agentic-loop-engineering-kit/terraform-standards/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/pallerana/agentic-loop-engineering-kit/terraform-standards"><img src="https://agentmods.dev/badge/rules/pallerana/agentic-loop-engineering-kit/terraform-standards.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.00398 |
| Opus 5.5 | $0.00000 | $0.00159 |
| Sonnet 5.5 | $0.00000 | $0.00080 |
| Haiku 4.5 | $0.00000 | $0.00040 |
Grade A, and why
terraform-standards 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.
What it actually says
CBA Terraform standards
Applies to infra// and platform infrastructure Terraform. Agent loop never runs terraform apply.
Patterns (from infra/)
- Modules: prefer existing modules under
automation/terraform/over inline resources. - Naming:
azurerm_*resources use consistentprimary/secondarypairing whenvar.secondary_regionis set. - Event Hub: consumer groups named explicitly (e.g.
my-service-centralonmy-service-statushub). - depends_on: explicit when module outputs are required before child resources.
- Tags: follow workspace tagging conventions in parent module variables.
Agent loop constraints
| Action | Allowed in loop |
|---|---|
terraform fmt / validate |
Yes (read-only validation) |
terraform plan |
Yes with human review of output |
terraform apply |
No — human gate only |
Edit prod *.tfvars |
No — denylist hook |
Review checklist
- No secrets in
.tffiles (use Key Vault / variable refs) - DR pattern respected when
secondary_regionnon-empty - knowledge-graph path from resource → consuming Java service documented in wiki if new
- DDog monitors updated in
DDog_1000896_iac_livewhen observability surface changes
Cross-links
infra/— foundation Terraformobservability-ddog.mdloop-kit/GATES.md— human inbox for infra flake
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 · 40 lines · 0 tokens per session scan A b83c5785faeb
terraform-standards is a cursor rule published in the GitHub repository pallerana/agentic-loop-engineering-kit (4 stars, last pushed 4mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 398 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-31.
Other cursor rules, from other repositories
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.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.