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/commands/srnichols/plan-forge/new-terraform-module)<a href="https://agentmods.dev/commands/srnichols/plan-forge/new-terraform-module"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-terraform-module/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/commands/srnichols/plan-forge/new-terraform-module"><img src="https://agentmods.dev/badge/commands/srnichols/plan-forge/new-terraform-module.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.00021 | $0.00871 |
| Opus 5 | $0.00010 | $0.00436 |
| Sonnet 5 | $0.00004 | $0.00174 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
new-terraform-module 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 yesterday.
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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create New Terraform Module
Scaffold a reusable Terraform module targeting Azure following CAF naming, provider version locking, and security defaults.
Required Information
Before generating, ask for:
- Module purpose — what Azure resource(s) does this module manage?
- Parameters — what
varinputs should callers provide? - Is this a root module or a child module? — root gets
providers.tfandversions.tf - Is this production-bound? — enables lifecycle protection and stricter networking defaults
Root Module Template
# versions.tf
terraform {
required_version = ">= 1.7.0"
required_providers {
azurerm = {
source = "hashicorp/azurerm"
version = "~> 4.0"
}
}
backend "azurerm" {
resource_group_name = "rg-tfstate-prod"
storage_account_name = "sttfstateprod"
container_name = "tfstate"
key = "myapp.{environment}.tfstate"
}
}
# providers.tf
provider "azurerm" {
features {}
use_oidc = true
}
# 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 dev, test, staging, or prod."
}
}
variable "workload_name" {
description = "Short workload name for 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 2–8 characters."
}
}
variable "location" {
description = "Azure region for all resources."
type = string
default = "eastus"
}
# locals.tf
locals {
suffix = substr(sha256("${var.workload_name}${var.environment_name}${data.azurerm_subscription.current.id}"), 0, 8)
resource_group_name = "rg-${var.workload_name}-${var.environment_name}"
# Add resource-specific names here following CAF abbreviations
common_tags = {
Environment = var.environment_name
Workload = var.workload_name
ManagedBy = "Terraform"
Repository = var.repository_url
}
}
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.
- yesterday First seen · 126 lines · 21 tokens per session scan A 185a85ac29ba
new-terraform-module is a command published in the GitHub repository srnichols/plan-forge (5 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 871 once invoked, about $0.0001 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-09-08.
Other commands, from other repositories
gentle-sdd-ff
Fast-forward all SDD planning phases — proposal through tasks.
sdd-explore
Explore and investigate an idea or feature — reads codebase and compares approaches.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
modernization-flow
Workflow for converting, modernizing, upgrading, or re-architecting code (e.g. C++→Java, monolith→microservices), etc.
ui-aqa-flow-test-report-analysis
Phase 7 Test Report Analysis of ui-aqa-flow.
modernization-flow-grouping
Phase 4 Class Grouping of modernization-flow.