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/NickCrew/Claude-CortexWrote 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/nickcrew/claude-cortex/docker-expert)<a href="https://agentmods.dev/agents/nickcrew/claude-cortex/docker-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/docker-expert/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/nickcrew/claude-cortex/docker-expert"><img src="https://agentmods.dev/badge/agents/nickcrew/claude-cortex/docker-expert.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.00026 | $0.00677 |
| Opus 5.5 | $0.00010 | $0.00271 |
| Sonnet 5.5 | $0.00005 | $0.00135 |
| Haiku 4.5 | $0.00003 | $0.00068 |
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 1mo 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 1mo ago First seen · 106 lines · 26 tokens per session scan A 4f94f78b99e2
docker-expert is an agent published in the GitHub repository NickCrew/Claude-Cortex (61 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 677 once invoked, about $0.0001 per session on Opus 5.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
build-orchestrator
Use this agent when you need assistance with Docker and Make command management during development. This includes analyzing Dockerfiles for optimization opportunities, managing container lifecycles, handling volumes and data persistence, monitoring logs, and determining when rebuilds are necessary versus simple…
docker-compose-expert
Docker and Docker Compose expertise for homelab container infrastructure.
kube
Designs and audits Kubernetes cluster architectures — RBAC policies, CNI networking, workload configuration, and operators with explicit reliability tradeoffs. Use when designing a cluster, auditing RBAC, or rightsizing workloads. Trigger with "design a Kubernetes cluster", "audit our RBAC".
devops-engineer
Implements infrastructure changes - Dockerfiles, Aspire config, CI/CD workflows, health checks, env vars. Use for infra work that stays within deployment and orchestration files.
k8s-engineer
Kubernetes specialist for container orchestration, cluster management, and deployment strategies. Expert in GKE, EKS, manifest creation, Helm charts, operators, and Kubernetes best practices.
aws-cloud-architect
AWS cloud infrastructure architect specializing in designing, implementing, and optimizing scalable AWS solutions. Use for AWS service selection, architecture design, cost optimization, and security best practices for EC2, EKS, Fargate, and other AWS services.