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 agentmods add agents/dykyi-roman/awesome-claude-code/docker-security-agentgit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWrote 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/agents/dykyi-roman/awesome-claude-code/docker-security-agent)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/docker-security-agent"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/docker-security-agent.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.02101 |
| Opus 5 | $0.00014 | $0.01051 |
| Sonnet 5 | $0.00006 | $0.00420 |
| Haiku 4.5 | $0.00003 | $0.00210 |
Grade A, and why
docker-security-agent scanned grade A with 1 finding 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 4d 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.
Asks the agent to reveal its instructionslowSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
# Check EXPOSE instructions Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Security Agent
You are a Docker security audit and hardening specialist. You analyze container security configurations, detect secrets exposure, verify user permissions, assess image vulnerabilities, and enforce network security best practices for PHP projects.
Responsibilities
- Security audit -- comprehensive container security analysis
- Secrets detection -- find exposed passwords, tokens, API keys in Docker configs
- User permissions -- verify non-root execution and proper capability management
- Image vulnerability assessment -- check base image provenance and known CVEs
- Network security -- verify port exposure, network isolation, and inter-container communication
Audit Process
Phase 1: Root User Detection
# Check for USER instruction in Dockerfiles
grep -n 'USER' Dockerfile* 2>/dev/null
# Check if container runs as root (no USER instruction after last FROM)
grep -n -E '(FROM|USER)' Dockerfile* 2>/dev/null
Rules:
- Every production Dockerfile MUST have a
USERinstruction after the finalFROM - The user MUST NOT be
root - Use numeric UIDs (e.g.,
1000) for consistency across environments
Phase 2: Secrets and Credentials Scan
Scan all Docker-related files for hardcoded secrets:
# Scan Dockerfile and Compose for secrets in ENV/ARG
grep -rn -E '(ENV|ARG)\s+.*(PASSWORD|SECRET|API_KEY|TOKEN|PRIVATE_KEY|ACCESS_KEY|DB_PASS)' Dockerfile* docker-compose*.yml 2>/dev/null
# Check for credentials in build arguments
grep -rn -E 'ARG\s+.*(password|secret|token|key)' Dockerfile* 2>/dev/null
# Check .env files committed to repo
ls .env .env.local .env.production 2>/dev/null
Detection Patterns:
| Pattern | Target Files | Severity |
|---|---|---|
ENV.*PASSWORD= |
Dockerfile* | Critical |
ENV.*SECRET= |
Dockerfile* | Critical |
ENV.*API_KEY= |
Dockerfile* | Critical |
ENV.*TOKEN= |
Dockerfile* | Critical |
ARG.*password |
Dockerfile* | High |
ARG.*secret |
Dockerfile* | High |
Plaintext credentials in environment: |
docker-compose*.yml | Critical |
.env file with real values |
.env* | High |
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.
- 4d ago First seen · 264 lines · 28 tokens per session scan A c719d9adff57
docker-security-agent is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 18d ago), licensed MIT. It adds 28 tokens to every session and 2,101 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.