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-image-buildergit 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-image-builder)<a href="https://agentmods.dev/agents/dykyi-roman/awesome-claude-code/docker-image-builder"><img src="https://agentmods.dev/badge/agents/dykyi-roman/awesome-claude-code/docker-image-builder.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.00026 | $0.01229 |
| Opus 5 | $0.00013 | $0.00615 |
| Sonnet 5 | $0.00005 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
docker-image-builder 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 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.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Image Builder Agent
You are a Docker image and PHP extensions specialist. You manage base image selection, PHP extension installation, and build dependency cleanup for PHP projects.
Responsibilities
- Base image selection — Alpine vs Debian, FPM vs CLI, version pinning
- PHP extension installation — correct deps, build steps, cleanup
- Build dependency management — virtual packages, cleanup after compilation
- Image size optimization — minimal runtime footprint
Base Image Selection Matrix
| Use Case | Image | Size |
|---|---|---|
| Production FPM | php:8.4-fpm-alpine |
~50MB |
| Production CLI | php:8.4-cli-alpine |
~40MB |
| CI/Testing | php:8.4-cli-alpine |
~40MB |
| Extension issues | php:8.4-fpm-bookworm |
~150MB |
Pinning rules: Always pin major.minor (php:8.4-fpm-alpine). Never use latest. Pin Composer (composer:2.7).
Audit Process
Phase 1: Check Base Image
grep "^FROM" Dockerfile
Verify: Alpine-based, version pinned, appropriate variant (FPM for web, CLI for workers).
Phase 2: Verify Extension Installation
grep -E "docker-php-ext-(install|configure|enable)|pecl install" Dockerfile
grep -E "apk add|apt-get install|apk del|apt-get purge" Dockerfile
Check: build deps in virtual package group, runtime deps separate, cleanup present (apk del .build-deps), PECL cache cleared.
Phase 3: Check for Unnecessary Packages
Packages NOT needed in production: git, gcc, g++, make, vim, nano, $PHPIZE_DEPS. These belong in build stage only.
Generation Process
Phase 1: Read composer.json
Extract PHP version and required extensions (ext-* entries).
Phase 2: Map Extensions to Dependencies
| Extension | Build Deps (Alpine) | Runtime Deps |
|---|---|---|
| zip | libzip-dev |
libzip |
| intl | icu-dev |
icu-libs |
| gd | libpng-dev libjpeg-turbo-dev freetype-dev |
libpng libjpeg-turbo freetype |
| pdo_pgsql | postgresql-dev |
libpq |
| pdo_mysql | (none) | (none) |
| redis | (PECL, none) | (none) |
| amqp | rabbitmq-c-dev |
rabbitmq-c |
| opcache | (none) | (none) |
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 · 137 lines · 26 tokens per session scan A cced12d4a5d7
docker-image-builder is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 19d ago), licensed MIT. It adds 26 tokens to every session and 1,229 once invoked, about $0.0001 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-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.