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/pallerana/agentic-loop-engineering-kit/terraform-standardsgit clone --depth 1 https://github.com/pallerana/agentic-loop-engineering-kitWhat 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.00000 | $0.00398 |
| Opus 5 | $0.00000 | $0.00199 |
| Sonnet 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 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.
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.
- 2d 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 2mo 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
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
redteam-compute
Compute security sub-agent for an Azure red team engagement. Covers VMs, VMSS, App Service, and Functions. Finds disk encryption gaps, exposed managed identities, plaintext secrets, runCommand exposure, FTP/remote-debug, and missing auth. Containers and Kubernetes (AKS, ACR, Container Apps/Instances) are owned by the…
cloud-workload-cost-estimator
Pre-deployment cost modeling for new workloads, architecture alternatives, and migration plans. Produces estimates the FinOps and Engineering teams both trust, with explicit assumptions and sensitivity ranges.
union-mcp-v2
Rules for using the Union MCP v2 server to run compute- or io-intensive workloads on Flyte.
tanaakk-multi-cloud-iam
クラウド非依存のマルチクラウド IAM 標準（Alibaba/AWS/GCP/Azure に依存しない）.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.