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 instructions/srnichols/plan-forge/terraformgit clone --depth 1 https://github.com/srnichols/plan-forgeWhat 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.01695 | $0.01695 |
| Opus 5 | $0.00847 | $0.00847 |
| Sonnet 5 | $0.00339 | $0.00339 |
| Haiku 4.5 | $0.00169 | $0.00169 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 238 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.7.0"
required_providers {
azurerm = {
source = "hashicorp/azurerm"
version = "~> 4.0" # pin to minor; review major bumps
}
azapi = {
source = "Azure/azapi"
version = "~> 2.0" # for preview/new resources not in azurerm
}
random = {
source = "hashicorp/random"
version = "~> 3.6"
}
}
# ✅ 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" {
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.
- 2d 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 (5 stars, last pushed 22d ago), licensed MIT. It adds 1,695 tokens to every session, about $0.0085 per session on Opus 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
dotnet-skills AGENTS.md
Instructions for managedcode/dotnet-skills, covering agents.md, purpose, solution topology, rule precedence and path and linking rules.
dotnet-skills copilot-instructions.md
Instructions for managedcode/dotnet-skills: Use AGENTS.md as the repository-wide source of truth for workflow, catalog structure, release policy, and skill maintenance rules.
Perigon.CLI copilot-instructions.md
Instructions for AterDev/Perigon.CLI, covering github copilot instructions, general guidelines, 技术栈, 项目结构与分层 and 代码风格约定.
copilot-instructions copilot-instructions.md
Instructions for SebastienDegodez/copilot-instructions, covering copilot instructions, language policy, development code generation and workflow implementation.
maf-doctor maf-deployment.instructions.md
Always-loaded production-deployment patterns for MAF 1.3.0. Auto-applies to Program.cs, DI registration files, and infra config. Covers ManagedIdentityCredential, MaxTokens caps, secret handling, OpenTelemetry wiring, and the analyzer rules that catch regressions at write time.
maf-doctor copilot-instructions.md
Instructions for joslat/maf-doctor, covering maf 1.3.0 migration — auto-loaded constraints, maf 1.3.0 — constraints & breaking changes reference, hard constraints (never violate), fan-out / fan-in rules (silent failure risk) and key breaking changes.