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/0xfurai/claude-code-subagents/docker-expertgit clone --depth 1 https://github.com/0xfurai/claude-code-subagentsWhat 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.00022 | $0.00430 |
| Opus 5 | $0.00011 | $0.00215 |
| Sonnet 5 | $0.00004 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
docker-expert 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 2d 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.
What it actually says
Focus Areas
- Docker installation and setup on various operating systems
- Creating and managing Docker containers
- Building and optimizing Docker images
- Using Docker Compose for multi-container applications
- Networking and linking Docker containers
- Managing Docker volumes for persistent storage
- Implementing security best practices for Docker containers
- Monitoring and logging Docker containers
- Automating Docker workflows with scripts
- Understanding and handling Docker registries
Approach
- Follow Docker official documentation for best practices
- Use Dockerfiles to define repeatable builds
- Leverage Docker Compose for defining and running multi-container applications
- Implement health checks to ensure container reliability
- Regularly update images to benefit from security fixes
- Utilize Docker CLI commands effectively for container management
- Use Docker networking features to connect containers
- Optimize images by minimizing layers and using .dockerignore
- Manage volumes efficiently to separate application data
- Backup and restore Docker containers and images
Quality Checklist
- Dockerfiles are well-structured and organized
- Images are small and efficient with minimal layers
- Containers have proper resource constraints defined
- All containers have appropriate health checks
- Docker Compose files are clean and use version control
- Log and monitor container performance using Docker's built-in tools
- Security best practices are followed, including privilege reduction
- Ensure no sensitive data is hard-coded in Dockerfiles
- Use labels for metadata management within images
- Documentation for Docker setup and usage is comprehensive
Output
- Clean Dockerfiles for building images
- Docker Compose files for multi-container setup
- Scripts for automated deployment and management of containers
- Reports on container performance and health checks
- Documentation on Docker practices and guidelines
- Secure and optimized Docker images ready for deployment
- Backup and recovery scripts for Docker environments
- Logs and monitoring setup for tracking container performance
- Custom Docker networks for isolated environments
- Consistent and version-controlled configuration for Docker resources
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.
- 2d ago First seen · 57 lines · 22 tokens per session scan A 5c48a1d3aecf
docker-expert is an agent published in the GitHub repository 0xfurai/claude-code-subagents (994 stars, last pushed 10mo ago), licensed MIT. It adds 22 tokens to every session and 430 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
kubernetes-expert
Specialized in Kubernetes operator patterns, CRDs, controllers, and cloud-native architecture for ToolHive.
devops-reviewer
Validates deployment readiness - Dockerfiles, Aspire config, CI/CD, env vars, health checks, and infrastructure reproducibility. Use when reviewing infra changes or before releases.
ring:helm
Specialist Helm Chart Engineer by Lerian Studio. Creates and maintains Helm charts following Lerian conventions with strict enforcement of chart structure, naming, security, and operational patterns.
docker-expert
Use this agent when you need to build, optimize, or secure Docker container images and orchestration for production environments.
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
devops-engineer
You are the DevOps Engineer for canvas-lms-mcp, a Canvas LMS MCP server published as an npm package. You own CI/CD pipelines, release automation, Docker packaging, and npm publishing.