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 skills add uttej-badwane/secure-cloud-prompt-engineering --skill iac-security-reviewgit clone --depth 1 https://github.com/uttej-badwane/secure-cloud-prompt-engineeringWrote 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/uttej-badwane/secure-cloud-prompt-engineering/iac-security-review)<a href="https://agentmods.dev/skills/uttej-badwane/secure-cloud-prompt-engineering/iac-security-review"><img src="https://agentmods.dev/badge/skills/uttej-badwane/secure-cloud-prompt-engineering/iac-security-review/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/uttej-badwane/secure-cloud-prompt-engineering/iac-security-review"><img src="https://agentmods.dev/badge/skills/uttej-badwane/secure-cloud-prompt-engineering/iac-security-review.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.00193 | $0.01937 |
| Opus 5 | $0.00097 | $0.00968 |
| Sonnet 5 | $0.00039 | $0.00387 |
| Haiku 4.5 | $0.00019 | $0.00194 |
Grade A, and why
iac-security-review 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 10d 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 — 206 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IaC Security Review Skill
You are an expert Infrastructure as Code security reviewer. Perform thorough security assessments of IaC files, identifying vulnerabilities, misconfigurations, and compliance gaps. Prioritize findings by severity and provide actionable remediation guidance.
Workflow
Step 1: Identify Scope
Scan the current directory or the files the user provides. Classify each file by IaC type:
| File Pattern | Type |
|---|---|
*.tf, *.tfvars |
Terraform |
*.yaml, *.yml with apiVersion |
Kubernetes |
Dockerfile* |
Docker |
*.yaml with AWSTemplateFormatVersion |
CloudFormation |
*.yaml with hosts: or tasks: |
Ansible |
Chart.yaml, values.yaml |
Helm |
.github/workflows/*.yml |
GitHub Actions |
.gitlab-ci.yml |
GitLab CI |
docker-compose*.yml |
Docker Compose |
kustomization.yaml |
Kustomize |
Report the scope summary to the user before proceeding.
Step 2: Run Security Checks
For each file, evaluate against the checklists in references/security-checks.md.
Organize findings by these categories:
- CRITICAL — Immediate exploitation risk (public exposure, no auth, secrets in code)
- HIGH — Significant risk requiring prompt remediation (overly permissive IAM, missing encryption)
- MEDIUM — Best practice violations (missing logging, no resource limits)
- LOW — Hardening recommendations (tags, naming conventions)
- INFO — Observations and positive findings
Step 3: Map to Compliance Frameworks
For each finding, map to applicable compliance controls using references/compliance-mapping.md.
Only include frameworks the user requests. If none specified, default to CIS + NIST 800-53.
Step 4: Generate Report
Use the scripts/generate_report.py script to produce a structured report:
python3 {SKILL_BASE_PATH}/scripts/generate_report.py \
--format markdown \
--output /tmp/iac-security-review-report.md
If the script is unavailable, generate the report directly in this format:
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 206 lines · 193 tokens per session scan A 2283ecd52408
iac-security-review is a skill published in the GitHub repository uttej-badwane/secure-cloud-prompt-engineering (2 stars, last pushed 6mo ago), licensed MIT. It adds 193 tokens to every session and 1,937 once invoked, about $0.0010 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 skills, from other repositories
devops-engineer
Creates Dockerfiles, configures CI/CD pipelines, writes Kubernetes manifests, and generates Terraform/Pulumi infrastructure templates. Handles deployment automation, GitOps configuration, incident response runbooks, and internal developer platform tooling. Use when setting up CI/CD pipelines, containerizing…
implementing-infrastructure-as-code-security-scanning
This skill covers implementing automated security scanning for Infrastructure as Code (IaC) templates using tools like Checkov, tfsec, and KICS. It addresses detecting misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts before deployment, establishing policy-based governance, and…
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
performing-container-security-scanning-with-trivy
Scan container images, filesystems, and Kubernetes manifests for vulnerabilities, misconfigurations, exposed secrets, and license compliance issues using Aqua Security Trivy with SBOM generation and CI/CD integration.
supply-chain-attack-recon
External recon for software supply-chain attack surface — package-namespace squatting candidates, dependency-confusion vulnerabilities, GitHub Actions injection openings, container image registry exposure, SBOM mining, internal-package-name leakage, and CI/CD configuration exposure. Reconnaissance and identification…