Developer Config Quality Suite
Three adversarial gates that pressure-test the config that powers your stack — before it ships. The Dockerfile gate catches root users, bloat, leaked secrets and fragile layers; the AGENTS.md gate flags ambiguous rules, contradictions and missing guardrails in your agent instructions; and the Cloud & Infrastructure Config Security Gate surfaces risky defaults, over-broad permissions and exposure in your IaC. Each returns a clear PASS / REVISE / BLOCK verdict. Built for developers, platform and DevOps engineers who want a second set of eyes on the files that quietly control everything.
Works with every agent that reads SKILL.md — Claude Code, Cursor, Codex CLI, Gemini CLI, GitHub Copilot, Windsurf, OpenClaw, and more.
One payment, lifetime access. 3 skills unlock instantly in your library.
30-day refund guarantee
Instant unlock in your library
Free updates from the creator
What's included
3 skills
An adversarial gate that audits cloud and infrastructure-as-code config — Terraform, Kubernetes, IAM, security groups, buckets — for the misconfigurations that cause real breaches, and returns a structured PASS/REVISE/BLOCK verdict with severities and exact fixes before anything reaches your environment.
An adversarial reviewer for Dockerfiles and container builds. It flags root users, image bloat, unpinned or cache-busting layers, leaked secrets, and missing hardening, then returns a PASS / FIX / BLOCK verdict — before you build or push the image.
An adversarial reviewer for AGENTS.md and agent instruction files. It flags ambiguous or contradictory rules, missing guardrails, vague tool and scope definitions, and untestable instructions, then returns a PASS / REVISE / BLOCK verdict — before the config drives your agent.
See it in action
You say
resource "aws_s3_bucket" "logs" { bucket = "app-prod-logs" acl = "public-read" } resource "aws_iam_policy" "app" { policy = jsonencode({ Statement = [{ Effect = "Allow", Action = "", Resource = "" }] }) }
Your agent does
VERDICT: BLOCK
SUMMARY: A log bucket is publicly readable and an IAM policy grants unrestricted access to every action on every resource. Both are critical and this config is not safe to apply.
FINDINGS:
- [SEVERITY: CRITICAL] aws_s3_bucket.logs — acl = "public-read" exposes production logs (which often contain tokens and PII) to the public — set acl to "private" and attach a public-access block.
- [SEVERITY: CRITICAL] aws_iam_policy.app — Action "" on Resource "" is full admin access — scope to the specific actions and ARNs the workload actually needs.
BLOCKERS: both CRITICAL findings must be fixed before apply.
SAFE TO APPLY: no
How to install
Drop the file into your AI Agent. Works with Claude, Cursor, ChatGPT, and 20+ more.