Borrowing it
Nothing to install: this file belongs to stefaniuk/loadout. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stefaniuk/loadout/main/.github/instructions/terraform.instructions.mdgit clone --depth 1 https://github.com/stefaniuk/loadoutWrote 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/instructions/stefaniuk/loadout/terraform)<a href="https://agentmods.dev/instructions/stefaniuk/loadout/terraform"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/terraform/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/instructions/stefaniuk/loadout/terraform"><img src="https://agentmods.dev/badge/instructions/stefaniuk/loadout/terraform.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.10716 | $0.10716 |
| Opus 5.5 | $0.04286 | $0.04286 |
| Sonnet 5.5 | $0.02143 | $0.02143 |
| Haiku 4.5 | $0.01072 | $0.01072 |
Grade A, and why
loadout terraform.instructions.md 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.
How it starts
The opening of the file, as written. The whole thing — 787 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform Engineering Instructions (AWS) ☁️
These instructions define the default engineering approach for building and evolving AWS infrastructure using Terraform (Infrastructure as Code).
They must remain applicable to:
- Terraform configuration (
.tf), variables, and modules - Backend/state, environments, and release workflows
- Security, networking, identity, logging, and compliance controls
- Operational readiness (monitoring, alerting, runbooks)
- Documentation and diagrams for infrastructure and operations
They are non-negotiable unless an exception is explicitly documented (with rationale and expiry) in an ADR/decision record.
Identifier scheme. Every normative rule carries a unique tag in the form [TF-<prefix>-NNN], where the prefix maps to the containing section (for example OP for Operating Principles, LCL for Local-first developer experience, QG for Quality Gates, continuing through AI for AI-assisted expectations). Use these identifiers when referencing, planning, or validating requirements.
0. Quick reference (apply first) 🧠
This section exists so humans and AI assistants can reliably apply the most important rules even when context is tight.
- [TF-QR-001] Specification first: if a requirement is not specified (or agreed), do not invent it ([TF-OP-005]).
- [TF-QR-002] Small, safe changes: prefer incremental evolution over big rewrites ([TF-OP-003]).
- [TF-QR-003] Deterministic and reproducible: the same inputs must produce the same plan ([TF-OP-002], [TF-OP-008]–[TF-OP-009]).
- [TF-QR-004] Run the quality gates after any Terraform change and iterate to clean ([TF-QG-001]–[TF-QG-008]).
- [TF-QR-005] Plan-first discipline: all changes must be reviewed via
terraform planoutput ([TF-BEH-001]–[TF-BEH-003]). - [TF-QR-006] London-only residency: all infrastructure must be in
eu-west-2; no other region without an ADR ([TF-REG-001]–[TF-REG-002]). - [TF-QR-007] Secure-by-default: least privilege, encryption, auditable changes ([TF-OP-004], [TF-SEC-001]–[TF-SEC-026]).
- [TF-QR-008] No snowflakes: no manual changes in the AWS Console that are not represented in Terraform ([TF-OP-006]).
- [TF-QR-009] Remote state, isolated per environment: encrypted, versioned, access-controlled ([TF-STATE-001]–[TF-STATE-008]).
- [TF-QR-010] Observability baseline: CloudWatch logs, metrics, alarms, dashboards, and runbook references ([TF-OBS-001]–[TF-OBS-067]).
- [TF-QR-011] IaC or nothing: every AWS change must flow through Terraform under version control ([TF-OP-007]).
- [TF-QR-012] Avoid common anti-patterns: hardcoded ARNs, floating versions, mega-modules, secrets in
.tfvars(§20).
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 · 787 lines · 10,716 tokens per session scan A b06af6a439ad
loadout terraform.instructions.md is an instructions file published in the GitHub repository stefaniuk/loadout (1 stars, last pushed yesterday), licensed MIT. It adds 10,716 tokens to every session, about $0.0429 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-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.