Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/makigjuro/cloudstack-ai-pluginsnpx agentmods add skills/makigjuro/cloudstack-ai-plugins/add-terraform-moduleWrote 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/skills/makigjuro/cloudstack-ai-plugins/add-terraform-module)<a href="https://agentmods.dev/skills/makigjuro/cloudstack-ai-plugins/add-terraform-module"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/add-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/skills/makigjuro/cloudstack-ai-plugins/add-terraform-module"><img src="https://agentmods.dev/badge/skills/makigjuro/cloudstack-ai-plugins/add-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.00048 | $0.01038 |
| Opus 5.5 | $0.00019 | $0.00415 |
| Sonnet 5.5 | $0.00010 | $0.00208 |
| Haiku 4.5 | $0.00005 | $0.00104 |
Grade A, and why
add-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 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add Terraform Module
Scaffold a new Terraform module following project conventions.
Arguments
{module-name}— Name of the module (required, e.g.,redis,service-bus,postgresql){description}— What this module provisions (optional)
Configuration
Read cloudstack.json from the project root at the start of execution. Extract:
TF_PATH=infrastructure.terraformPath(default:infra/terraform/modules)TG_PATH=infrastructure.terragruntPath(default:infra/terragrunt)IAC_WRAPPER=infrastructure.iacWrapper(default:none)CLOUD=infrastructure.cloud(default:azure)
If cloudstack.json does not exist, auto-detect by scanning the project structure.
Process
-
Read existing modules in
{TF_PATH}/to follow established patterns. -
Create the module directory:
{TF_PATH}/{module-name}/
├── variables.tf
├── main.tf
├── outputs.tf
- variables.tf — Always include these standard variables:
variable "environment" {
description = "Environment name (e.g. dev, staging, prod)"
type = string
}
variable "location" {
description = "Cloud region (e.g. westeurope, us-east-1)"
type = string
}
variable "project" {
description = "Project prefix for resource naming"
type = string
}
variable "tags" {
description = "Common tags applied to all resources"
type = map(string)
default = {}
}
Add module-specific variables after the standard ones.
- main.tf — Follow the naming convention from existing modules. Derive a location short code from the region (e.g.,
westeurope->weu,us-east-1->use1):
locals {
location_short = # derive from var.location or use a lookup map
name = "${var.project}-{resource-abbrev}-${var.environment}-${local.location_short}"
}
Scan existing modules to discover the project's established naming convention and location short mapping. Use that pattern.
- outputs.tf — Export
name,id, and any connection strings or keys needed by downstream modules.
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 · 138 lines · 48 tokens per session scan A 04b3df3ef6d9
add-terraform-module is a skill published in the GitHub repository makigjuro/cloudstack-ai-plugins (1 stars, last pushed 5d ago), licensed MIT. It adds 48 tokens to every session and 1,038 once invoked, about $0.0002 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 skills, from other repositories
karpenter
Design, install, debug, review, plan capacity, audit scaling history, migrate from Cluster Autoscaler, and upgrade Karpenter v1.x on EKS. Covers NodePool, EC2NodeClass, NodeClaim, Spot diversity, disruption strategy, Pod Identity/IRSA, interruption queue, private clusters, AMI rotation, and GitOps integration. Use…
aws
Structured guidance for AWS CloudFront distributions, WAF web ACLs, Lambda@Edge, CloudFront Functions, Firewall Manager multi-account enforcement, and IAM/IRSA patterns. Covers OAC, cache policies, security headers, managed rule groups, rate limiting, FMS FIRST/MIDDLE/LAST ownership model, and production-ready…
secrets
Secrets strategy, External Secrets Operator scaffolding, Sealed Secrets seal/rotate/backup, rotation runbooks, and Kubernetes-side secrets audit.
azure
Azure identity (Workload Identity, OIDC, Entra ID), resource tagging, AKS platform patterns, RBAC scoping, and production-readiness review — with Terraform generation.
openshift
OpenShift SCC diagnosis and hardening, Route TLS patterns, OpenShift GitOps app delivery, and cluster upgrade validation.
runtime-security
Detect and respond to in-container threats at the syscall level using Falco (eBPF-based, CNCF, open-source, no license cost). Covers Falco installation on EKS/GKE with eBPF driver, custom rule authoring, alert routing via Falcosidekick, rule debugging, and bridging Falco runtime signals to Kyverno admission…