Infrastructure review toolkit
Three local, read-only reviews to run before a change reaches production: SQL migrations that lock a table or destroy data, Terraform plans that destroy or open resources, and Dockerfile and Compose settings that run as root or leak secrets. Each one runs on your machine, reads only the files you name and changes nothing. Needs Python 3.9+.
Works with any agent that signs in to Agensi, such as Claude, ChatGPT, Claude Code, Cursor and Codex CLI.
One payment, lifetime access. 3 skills unlock instantly in your library.
What's included
3 skillsFinds unpinned images, root users, secrets in ENV, privileged containers and exposed database ports, with a fix for each.
Flags migration statements that lock tables or lose data, with a safer pattern for each. PostgreSQL and MySQL.
Terraform plan review: lists what a plan will destroy, replace or open (public access, wildcard IAM, encryption off).
See it in action
Dockerfile and Compose Audit
Example session with this skill installed
/dockerfile-audit Dockerfile
- Read your context and instructions
- Compiled the dockerfile and compose
Illustrative. The Dockerfile is invented (the token in it is not a real one); the report below is what the script prints for it. Secret values are hidden.
DOCKER AUDIT (1 file(s): 1 high, 4 medium, 7 info)
examples/bad/Dockerfile [dockerfile]
HIGH line 4 secret-in-image-metadata
ENV API_TOKEN=<value hidden>
why: A value set here is stored in the image layers and shown by the image history, so anyone who can pull the image can read it.
better: Pass secrets at run time (environment from your orchestrator or a secret mount), or use a build secret mount for build-time needs.
MEDIUM line 1 unpinned-base-image
FROM node
why: A base image with no tag, or the latest tag, changes without notice, so the same Dockerfile builds different images over time.
better: Pin a version tag (for example python:3.12-slim), and a digest if you need exact repeatability.
MEDIUM line 1 runs-as-root
FROM node (last stage)
why: The container runs as the administrator account unless a USER line says otherwise, so a flaw in the app gives wide access.
better: Create a non-administrator user and switch to it with USER before the final command.
MEDIUM line 7 apt-update-alone
RUN apt-get update
why: An update on its own layer is cached, so a later install can use a stale package list and fail or install old versions.
better: Run update and install in the same RUN instruction.
MEDIUM line 11 expose-ssh
EXPOSE 22 8080
why: Port 22 suggests an SSH server inside the container, which is rarely needed and widens the attack surface.
better: Use the container runtime's own exec or a debug sidecar instead of running SSH in the image.
INFO line 1 no-healthcheck
FROM node (last stage)
why: A service with no health check cannot tell the platform when it is broken.
better: Add a HEALTHCHECK, or define the check in your orchestrator.
INFO line 1 no-digest
(whole file)
why: Images are pinned by tag only; a tag can be moved by the registry owner.
better: For exact repeatability, pin by digest (image@sha256:...) and update it on purpose.
INFO line 5 cache-order
COPY . ...
why: Everything is copied before dependencies are installed, so any source change re-runs the install step.
better: Copy only the dependency manifest first, install, then copy the rest.
INFO line 8 apt-recommends
RUN apt-get install -y curl git
why: Recommended packages are installed too, which makes the image larger.
better: Add --no-install-recommends and list what you need.
INFO line 8 apt-lists-left
RUN apt-get install -y curl git
why: The package lists stay in the layer and add size.
better: End the same RUN by removing /var/lib/apt/lists.
INFO line 9 add-instead-of-copy
ADD config.yaml /app/config.yaml
why: ADD can unpack archives and fetch URLs, which surprises people. For plain files COPY says what it does.
better: Use COPY for local files.
INFO line 10 pip-cache
RUN pip install flask
why: pip keeps a download cache in the layer and adds size.
better: Add --no-cache-dir, or set PIP_NO_CACHE_DIR=1.
Limits: this reads the text of the files. It does not build the image, so it cannot see what a base image contains, what a build argument is set to, or which user the base image already uses. Values of variables named like secrets are hidden, but other instruction lines are echoed (up to 110 characters), so a token typed inside a RUN line can appear in the report. A clean report is not a security review.
Next steps
- Fix the high finding first and treat that token as exposed if it was ever real.
- Work through the medium findings, then the size and speed notes, using the reference file for each rule.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads these skills and uses them on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every skill in this bundle goes through our trust checks.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.