- Home
- Skills
- DevOps & Cloud
- CI/CD & Docker Security Linter
Works with the AI Agents you already use
CI/CD & Docker Security Linter
Lints Docker and GitHub Actions configurations for security risks, root escalations, and supply chain vulnerabilities.
$5
CI/CD & Docker Security Linter
Example session with this skill installed
Review the Dockerfile and .github/workflows/deploy.yml in this repo for security issues.
- Read your context and instructions
- Compiled the ci cd
[HIGH] Dockerfile - Line 1: Base image 'node:latest' is unpinned. Use a specific digest or version tag.
[CRITICAL] .github/workflows/deploy.yml - Line 12: Uses 'actions/checkout@v3' instead of a commit SHA. Pinned SHAs prevent supply chain attacks if the action is compromised.
Connects securely to your tools. The creator never sees your data.
About this skill
The problem
CI/CD pipelines and container configurations often harbor silent security risks outside of application source code. Misconfigured Dockerfiles or GitHub Actions workflows can lead to root escalations, supply chain attacks, and secret leakage.
What it does
- Identifies Dockerfiles running as root or using unpinned 'latest' base image tags.
- Flags dangerous docker-compose settings like privileged mode or Docker socket mounts.
- Detects insecure GitHub Actions patterns including pull_request_target misuse and unpinned commit SHAs.
- Scans for hardcoded secrets in ARG/ENV instructions and unsafe echoing of secrets in pipeline logs.
- Generates structured findings compatible with security-hygiene-checklist and security-audit-report formats.
Frameworks & tools
Docker, docker-compose, GitHub Actions, and Python.
Why this beats prompting it yourself
General LLM prompts often miss subtle CI/CD attack vectors like mutable tag hijacking or specific GitHub token permission over-scoping. This skill uses a codified checklist of high-impact misconfigurations, ensuring you don't overlook complex supply chain risks during a manual review.
Use cases
- Hardening container images before pushing to a production registry.
- Auditing GitHub Actions workflows for repositories accepting external pull requests.
- Reviewing docker-compose files to ensure proper network and volume isolation.
- Preparing a repository for public release or a security audit.
Known limitations
Uses regex-based parsing which may miss issues in complex YAML structures like anchors. It does not analyze the internal source code of third-party GitHub Actions.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for DevOps & Cloud.
Regex-based parsing may miss issues in complex YAML structures like anchors or multi-document files. Does not audit the actual code within third-party GitHub Actions.
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 this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
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.
Trust & safety
Security scan
Security scan passed 3 months ago