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 Quality-Max/free-qa-skills --skill iac-misconfig-scangit clone --depth 1 https://github.com/Quality-Max/free-qa-skillsWrote 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/quality-max/free-qa-skills/iac-misconfig-scan)<a href="https://agentmods.dev/skills/quality-max/free-qa-skills/iac-misconfig-scan"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/iac-misconfig-scan/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/quality-max/free-qa-skills/iac-misconfig-scan"><img src="https://agentmods.dev/badge/skills/quality-max/free-qa-skills/iac-misconfig-scan.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.00056 | $0.00656 |
| Opus 5 | $0.00028 | $0.00328 |
| Sonnet 5 | $0.00011 | $0.00131 |
| Haiku 4.5 | $0.00006 | $0.00066 |
Grade A, and why
iac-misconfig-scan 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 11d 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
- Find IaC files:
Dockerfile,docker-compose*.yml,*.tf, and.github/workflows/*.yml. - Review each against the checks below; report
file:line, severity, and the fix.
Containers (Dockerfile / Compose)
| Misconfiguration | Why it's risky |
|---|---|
No USER / runs as root |
Container compromise becomes host-level risk |
World-writable file modes (e.g. 0777) |
Tampering and privilege issues |
:latest or unpinned base image |
Non-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 ARG |
Secret leakage in image layers |
privileged: true, host network, or host path mounts (Compose) |
Container escape / host exposure |
ADD with a remote URL |
Silent, unverified remote fetch (prefer COPY) |
Terraform
| Misconfiguration | Why it's risky |
|---|---|
Public object storage / open ingress (0.0.0.0/0) |
Data exposure / open attack surface |
Hardcoded secrets in .tf or state |
Credential leakage |
| Unencrypted storage / disabled logging | Data-at-rest and audit gaps |
GitHub Actions
| Misconfiguration | Why it's risky |
|---|---|
| Actions pinned to a tag, not a commit SHA | Supply-chain tampering |
Broad permissions (or none set) |
Excess token scope |
Secrets echoed or used in pull_request_target with checkout of PR code |
Secret exfiltration |
- 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.
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.
- 11d ago First seen · 73 lines · 56 tokens per session scan A 0bf508516401
iac-misconfig-scan is a skill published in the GitHub repository Quality-Max/free-qa-skills (10 stars, last pushed 17d ago), licensed Apache-2.0. It adds 56 tokens to every session and 656 once invoked, about $0.0003 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-platform
Platform and delivery engineering — CI/CD pipelines, infrastructure as code, containers, environment parity, deployment strategies (blue/green, canary, rolling), rollback, secrets management, disaster recovery, autoscaling and cloud cost control. Use when working on pipelines, Dockerfiles, Terraform, Kubernetes…
docker-environments
Docker-aware Mémoire operation — CI/CD headless pipelines, shared MCP server, agent worker containers, and Figma bridge port-forwarding for containerized setups.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
accessibility
Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".
nextjs-deployment
Provides comprehensive patterns for deploying Next.js applications to production. Use when configuring Docker containers, setting up GitHub Actions CI/CD pipelines, managing environment variables, implementing preview deployments, or setting up monitoring and logging for Next.js applications. Covers standalone output…
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.