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/srnichols/plan-forgeWrote 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/srnichols/plan-forge/terraform)<a href="https://agentmods.dev/instructions/srnichols/plan-forge/terraform"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/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/srnichols/plan-forge/terraform"><img src="https://agentmods.dev/badge/instructions/srnichols/plan-forge/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.01732 | $0.01732 |
| Opus 5.5 | $0.00693 | $0.00693 |
| Sonnet 5.5 | $0.00346 | $0.00346 |
| Haiku 4.5 | $0.00173 | $0.00173 |
Grade A, and why
plan-forge 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 24d 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 — 246 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Terraform on Azure Best Practices
File Structure
infra/
├── main.tf ← resource definitions
├── variables.tf ← input variable declarations
├── outputs.tf ← output value declarations
├── providers.tf ← provider configuration
├── versions.tf ← required_providers with version locks
├── locals.tf ← computed/derived values
├── terraform.tfvars ← variable values (dev — never commit prod secrets)
└── modules/
├── networking/
│ ├── main.tf
│ ├── variables.tf
│ └── outputs.tf
└── compute/
├── main.tf
├── variables.tf
└── outputs.tf
Provider Configuration
# versions.tf — always lock provider versions
terraform {
required_version = ">= 1.16"
required_providers {
azurerm = {
source = "hashicorp/azurerm"
version = "~> 5.7" # latest GA major; register required RPs explicitly
}
azapi = {
source = "Azure/azapi"
version = "~> 2.13" # for preview/new resources not in azurerm
}
random = {
source = "hashicorp/random"
version = "~> 3.9"
}
}
# ✅ Remote state in Azure Blob Storage — never local state in CI
backend "azurerm" {
resource_group_name = "rg-tfstate-prod"
storage_account_name = "sttfstateprod"
container_name = "tfstate"
key = "myapp.prod.tfstate"
}
}
# providers.tf — use Managed Identity (no client_secret in code)
provider "azurerm" {
resource_providers_to_register = [
"Microsoft.Authorization",
"Microsoft.KeyVault",
"Microsoft.ManagedIdentity",
"Microsoft.Network",
"Microsoft.Storage",
]
features {}
use_oidc = true # workload identity federation in CI
}
Variable Declarations
# variables.tf
variable "environment_name" {
description = "The environment name (dev, test, staging, prod)."
type = string
validation {
condition = contains(["dev", "test", "staging", "prod"], var.environment_name)
error_message = "environment_name must be one of: dev, test, staging, prod."
}
}
variable "workload_name" {
description = "Short workload name used in resource naming (2-8 chars)."
type = string
validation {
condition = length(var.workload_name) >= 2 && length(var.workload_name) <= 8
error_message = "workload_name must be between 2 and 8 characters."
}
}
# ✅ sensitive = true on all secret variables
variable "db_admin_password" {
description = "Admin password for the database."
type = string
sensitive = true
}
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.
- 24d ago Changed · +8 lines · +37 tokens per session 267be6758c86
- 1mo ago First seen · 238 lines · 1,695 tokens per session scan A b5b5078ec68a
plan-forge terraform.instructions.md is an instructions file published in the GitHub repository srnichols/plan-forge (6 stars, last pushed today), licensed MIT. It adds 1,732 tokens to every session, about $0.0069 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.