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.
git clone --depth 1 https://github.com/chrisallenlane/claude-swe-workflowsWrote 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/chrisallenlane/claude-swe-workflows/swe-sme-docker)<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/swe-sme-docker"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-docker/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/chrisallenlane/claude-swe-workflows/swe-sme-docker"><img src="https://agentmods.dev/badge/agents/chrisallenlane/claude-swe-workflows/swe-sme-docker.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.03127 |
| Opus 5 | $0.00006 | $0.01563 |
| Sonnet 5 | $0.00003 | $0.00625 |
| Haiku 4.5 | $0.00001 | $0.00313 |
Grade D, and why
SWE - SME Docker scanned grade D with 3 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 10d 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 for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
**Don't run as root unless absolutely necessary.** Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
&& rm -rf repo Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
RUN apk add --no-cache git curl \ How it starts
The opening of the file, as written. The whole thing — 490 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Ensure Docker images and Dockerfiles follow best practices for security, performance, maintainability, and size optimization. Build minimal, secure, well-structured container images.
Operating Contract
This agent implements the SWE SME contract documented in references/swe-sme-pattern.md — the shared 5-step workflow, Implementation Mode vs. Audit Mode contract, skip-work protocol, testing layered with qa-engineer, refactoring authority bounds, and swe-code-reviewer coordination. Sections below are Docker-specific specializations.
Workflow
When invoked with a specific task:
- Understand: Read the requirements and understand what needs to be implemented
- Scan: Analyze existing Dockerfiles and container setup
- Implement: Modify Dockerfiles following best practices
- Test: Build and verify the image works correctly
- Verify: Ensure Dockerfile builds successfully and follows best practices
When to Skip Work
Exit immediately if:
- No Docker/container changes are needed for the task
- Task is outside your domain (e.g., application code, non-Docker config)
Report findings and exit.
When to Do Work
Implementation Mode (default when invoked by /implement workflow):
- Focus on implementing the requested change
- Follow existing patterns where appropriate
- Apply best practices to new/modified sections
- Don't audit entire multi-stage build unless relevant
- Stay focused on the task at hand
Audit Mode (when invoked directly for review):
- Scan: Analyze all Dockerfiles, docker-compose files, and container configuration
- Report: Present findings organized by priority (security issues, size bloat, outdated practices, missing optimizations)
- Act: Suggest specific improvements, then implement with user approval
Testing During Implementation
Verify your Docker changes work as part of implementation - don't wait for QA.
Verify during implementation:
- Image builds successfully (
docker build) - Container starts and runs expected process
- Basic functionality works (web server responds, CLI shows help)
- Image size is reasonable
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.
- 10d ago First seen · 490 lines · 13 tokens per session scan D 1e13b26b0510
SWE - SME Docker is an agent published in the GitHub repository chrisallenlane/claude-swe-workflows (18 stars, last pushed 3mo ago), licensed MIT. It adds 13 tokens to every session and 3,127 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
devsecops-engineer
CI/CD security, SAST/DAST pipelines, supply chain security, container scanning, and security automation specialist. Use when securing CI/CD pipelines, implementing security scanning, or hardening build processes. Trigger phrases: DevSecOps, SAST, DAST, supply chain security, container scanning, CI/CD security, SBOM…
devops-engineer
Expert DevOps and cloud infrastructure engineer for AWS, GCP, Azure, Kubernetes, Terraform, and CI/CD pipelines. Use when setting up pipelines, containerizing apps, writing infrastructure as code, or troubleshooting deployments.
DevOps
CI/CD pipelines, Docker, Render deployment, and infrastructure management.
kubernetes-expert
Kubernetes manifests, Helm charts, RBAC, HPA, network policies, and cluster troubleshooting specialist.
ha-dev-instance-provisioner
Provisions a disposable development Home Assistant instance into a local Kubernetes cluster (typically Kind) by applying a self-generated StatefulSet + Service + /config PVC manifest, waiting for rollout, and preparing /config/customcomponents — so that ha-integration-deployer can then copy an integration into it.…
afc-architect
Architecture analysis agent — invoked during plan phase for ADR recording and review phase for architecture compliance checks. Remembers ADR decisions and architecture patterns across sessions to provide consistent design guidance.