agentleFS
Quality-MaxQuality-Max/free-qa-skills/skills/iac-misconfig-scan/SKILL.md

iac-misconfig-scan

Skill13 starsChanged 20 days agoApache-2.0View on GitHub

Scan infrastructure-as-code — Dockerfiles, Compose, Terraform, and GitHub Actions — for security misconfigurations like running as root, world-writable files, unpinned actions, and hardcoded secrets. Pure Claude Code, no signup.

The file

Files
SKILL.md

IaC Misconfig Scan

Catch insecure infrastructure-as-code before it ships. Read-only: it flags misconfigurations with file:line, it doesn't change anything.

Prerequisites

  • None. Pure Claude Code — reads IaC files directly, no MCP required.

Trigger

  • "Scan my Dockerfile / Terraform / workflows for misconfigs"
  • "Is my infrastructure-as-code secure?"
  • "IaC security review"

Workflow

  1. Find IaC files: Dockerfile, docker-compose*.yml, *.tf, and .github/workflows/*.yml.
  2. Review each against the checks below; report file:line, severity, and the fix.

Containers (Dockerfile / Compose)

MisconfigurationWhy it's risky
No USER / runs as rootContainer compromise becomes host-level risk
World-writable file modes (e.g. 0777)Tampering and privilege issues
:latest or unpinned base imageNon-reproducible, unreviewed updates
Download-and-execute build step (remote script piped into a shell)Unverified remote code in the image
Hardcoded secrets / credentials in ENV or ARGSecret leakage in image layers
privileged: true, host network, or host path mounts (Compose)Container escape / host exposure
ADD with a remote URLSilent, unverified remote fetch (prefer COPY)

Terraform

MisconfigurationWhy it's risky
Public object storage / open ingress (0.0.0.0/0)Data exposure / open attack surface
Hardcoded secrets in .tf or stateCredential leakage
Unencrypted storage / disabled loggingData-at-rest and audit gaps

GitHub Actions

MisconfigurationWhy it's risky
Actions pinned to a tag, not a commit SHASupply-chain tampering
Broad permissions (or none set)Excess token scope
Secrets echoed or used in pull_request_target with checkout of PR codeSecret exfiltration
  1. Output a severity-ranked report:
## IaC Misconfig Scan

**1 high, 2 medium**

### HIGH
- Dockerfile:1 — base image uses ":latest"; pin to a digest for reproducible,
  reviewable builds.

### MEDIUM
- .github/workflows/ci.yml:7 — action pinned to a tag, not a commit SHA.
- docker-compose.yml:12 — service runs without a non-root USER.

Diagnostic only. Want IaC and SAST checks enforced on every PR? See QualityMax — qualitymax.io

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.