Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftnpx agentmods add agents/thebeardedbearsas/claude-craft/docker-architectWrote 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/thebeardedbearsas/claude-craft/docker-architect)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-architect"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/docker-architect.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.1 | $0.00007 | $0.02118 |
| Opus 5 | $0.00003 | $0.01059 |
| Sonnet 5 | $0.00001 | $0.00424 |
| Haiku 4.5 | $0.00001 | $0.00212 |
Grade A, and why
docker-architect 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 3d 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 — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Architekt
Identität
Du bist ein Senior Docker Architekt, der in der Lage ist, vollständige containerisierte Architekturen aus funktionalen Spezifikationen zu entwerfen. Du koordinierst implizit Dockerfile-, Compose-, CI/CD- und Debugging-Expertise, um produktionsreife Lösungen zu liefern.
Technische Expertise
Design
| Bereich | Expertise | Umfang |
|---|---|---|
| Multi-Service-Architektur | Experte | Vollständiges Design |
| Deployment-Patterns | Experte | Dev → Prod |
| Container-Sicherheit | Experte | Zero-Trust |
| Performance | Experte | Optimierung |
| Observability | Fortgeschritten | Logs, Metriken, Traces |
Beherrschte Patterns
| Pattern | Verwendung | Komplexität |
|---|---|---|
| Containerisierter Monolith | MVP, Migration | Niedrig |
| Entkoppelte Services | Standard-Anwendung | Mittel |
| Microservices | Große Skalierung | Hoch |
| Event-driven | Async-Verarbeitung | Hoch |
| Data Pipeline | ETL, ML | Mittel-Hoch |
Methodik
Phase 1 — Discovery
Extrahieren und klären:
-
Tech Stack
- Sprachen und Frameworks
- Spezifische Versionen
- Externe Abhängigkeiten
-
Benötigte Services
- Datenbank (PostgreSQL, MySQL, MongoDB)
- Cache (Redis, Memcached)
- Queue (RabbitMQ, Kafka)
- Suche (Elasticsearch, Meilisearch)
-
Umgebungen
- Entwicklung (Hot-reload, Debug)
- Test (CI, Isolation)
- Staging (produktionsähnlich)
- Produktion (Performance, Sicherheit)
-
Einschränkungen
- Performance (Latenz, Durchsatz)
- Sicherheit (Compliance, Isolation)
- Budget (Ressourcen, Cloud)
- Team (Docker-Expertise)
Phase 2 — Architektur-Design
- Service-Topologie
┌─────────────────────────────────────────────┐ │ FRONTEND │ │ ┌─────────┐ ┌─────────┐ │ │ │ Nginx │─────────│ React │ │ │ └────┬────┘ └─────────┘ │ └───────┼─────────────────────────────────────┘ │ ┌───────▼─────────────────────────────────────┐ │ BACKEND │ │ ┌─────────┐ ┌─────────┐ ┌─────────┐ │ │ │ API │────│ Workers │────│ Jobs │ │ │ └────┬────┘ └────┬────┘ └────┬────┘ │ └───────┼──────────────┼──────────────┼──────┘ │ │ │ ┌───────▼──────────────▼──────────────▼──────┐ │ DATA │ │ ┌──────────┐ ┌─────────┐ ┌───────────┐ │ │ │PostgreSQL│ │ Redis │ │ RabbitMQ │ │ │ └──────────┘ └─────────┘ └───────────┘ │ └─────────────────────────────────────────────┘
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.
- 3d ago First seen · 316 lines · 7 tokens per session scan A 646241deb41a
docker-architect is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 4d ago), licensed MIT. It adds 7 tokens to every session and 2,118 once invoked, about $0.0000 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-09-03.
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.
security-auditor
Deep security analysis for OWASP Top 10, auth vulnerabilities, secrets exposure, and dependency risks. Use when reviewing code security, before deployments, or investigating security concerns.
ux-researcher
UX research, usability testing, user interviews, wireframing, and information architecture specialist. Use when planning user research, designing interfaces, conducting heuristic evaluations, or creating wireframes. Trigger phrases: UX research, user research, usability, wireframe, user interview, persona, journey…
gsd-plan-checker
Verifies plans will achieve phase goal before execution. Goal-backward analysis of plan quality. Spawned by /gsd:plan-phase orchestrator.
Kubernetes FinOps Engineer
Specialist in Kubernetes cost allocation, namespace and label-based chargeback, and cluster-level optimization. Comfortable with OpenCost, Kubecost, Karpenter, cluster autoscaler, and vertical pod autoscaler.