borghei/Claude-Skills / engineering/terraform-patterns
terraform-patterns
VerifiedTerraform module design and review: complexity and documentation analysis plus an AWS-focused misconfiguration scan. Use when writing or reviewing Terraform modules or gating IaC changes.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.3 KB |
| examples/main.tf | other | 4.4 KB |
| references/terraform-patterns.md | markdown | 3.7 KB |
| scripts/tf_module_analyzer.py | script | 13.8 KB |
| scripts/tf_security_scanner.py | script | 17.1 KB |
examples/main.tf
View on GitHub# main.tf — Terraform config with deliberate security issues
#
# This Terraform configuration contains common security anti-patterns
# for the terraform-patterns skill scanner to detect:
# - Overly permissive CIDR blocks (0.0.0.0/0)
# - Public S3 bucket
# - Missing encryption (EBS, RDS, S3)
# - Hardcoded credentials
# - No logging or monitoring
# - Overly broad IAM policies
# - Missing tags
# - Default VPC usage
terraform {
required_version = ">= 1.5.0"
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 6.0"
}
}
}
provider "aws" {
region = "us-east-1"
# SECURITY ISSUE: hardcoded credentials
access_key = "AKIAIOSFODNN7EXAMPLE"
secret_key = "wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY"
}
# SECURITY ISSUE: security group allows all inbound traffic
resource "aws_security_group" "web" {
name = "web-sg"
description = "Web server security group"
ingress {
description = "SSH from anywhere"
from_port = 22
to_port = 22
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"] # ISSUE: SSH open to the world
}
ingress {
description = "HTTP"
from_port = 80
to_port = 80
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
}
ingress {
description = "HTTPS"
from_port = 443
to_port = 443
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"]
}
ingress {
description = "Database"
from_port = 5432
to_port = 5432
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"] # ISSUE: DB port open to the world
}
egress {
from_port = 0
to_port = 0
protocol = "-1"
cidr_blocks = ["0.0.0.0/0"]
}
}
# SECURITY ISSUE: public S3 bucket with no encryption
resource "aws_s3_bucket" "data" {
bucket = "acme-corp-customer-data"
# ISSUE: no tags
}
resource "aws_s3_bucket_public_access_block" "data" {
bucket = aws_s3_bucket.data.id
# ISSUE: public access not blocked
block_public_acls = false
block_public_policy = false
ignore_public_acls = false
restrict_public_buckets = false
}
# ISSUE: no server-side encryption configured
# (missing: aws_s3_bucket_server_side_encryption_configuration)
# ISSUE: no versioning enabled
# (missing: aws_s3_bucket_versioning)
# ISSUE: no access logging
# (missing: aws_s3_bucket_logging)
# SECURITY ISSUE: EC2 instance with no encryption, public IP, no IMDSv2
resource "aws_instance" "web" {
ami = "ami-0c55b159cbfafe1f0"
instance_type = "t3.large"
vpc_security_group_ids = [aws_security_group.web.id]
associate_public_ip_address = true # ISSUE: public IP assigned
# ISSUE: no encryption on root volume
root_block_device {
volume_size = 50
volume_type = "gp3"
encrypted = false # ISSUE: unencrypted EBS
}
# ISSUE: no IMDSv2 enforcement
# (missing: metadata_options { http_tokens = "required" })
# ISSUE: user data with inline secrets
user_data = <<-EOF
#!/bin/bash
echo "DB_PASSWORD=pr0duct10n_s3cret" >> /etc/environment
echo "API_KEY=sk-live-abc123def456" >> /etc/environment
EOF
# ISSUE: no tags
}
# SECURITY ISSUE: RDS with no encryption, public access, weak password
resource "aws_db_instance" "main" {
identifier = "acme-production-db"
engine = "postgres"
engine_version = "15.4"
instance_class = "db.t3.medium"
allocated_storage = 100
storage_type = "gp3"
db_name = "acme_production"
username = "admin"
password = "admin123" # ISSUE: weak hardcoded password
publicly_accessible = true # ISSUE: database publicly accessible
storage_encrypted = false # ISSUE: storage not encrypted
skip_final_snapshot = true # ISSUE: no final snapshot on deletion
backup_retention_period = 0 # ISSUE: no automated backups
# ISSUE: no multi-AZ for production
multi_az = false
# ISSUE: no tags
}
# SECURITY ISSUE: overly permissive IAM policy
resource "aws_iam_role" "app" {
name = "acme-app-role"
assume_role_policy = jsonencode({
Version = "2012-10-17"
Statement = [{
Action = "sts:AssumeRole"
Effect = "Allow"
Principal = { Service = "ec2.amazonaws.com" }
}]
})
}
resource "aws_iam_role_policy" "app" {
name = "acme-app-policy"
role = aws_iam_role.app.id
# ISSUE: wildcard permissions — grants full access to everything
policy = jsonencode({
Version = "2012-10-17"
Statement = [{
Effect = "Allow"
Action = "*"
Resource = "*"
}]
})
}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |