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 commands/thebeardedbearsas/claude-craft/docker-architecturegit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/commands/thebeardedbearsas/claude-craft/docker-architecture)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/docker-architecture"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/docker-architecture.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.00008 | $0.03133 |
| Opus 5 | $0.00004 | $0.01566 |
| Sonnet 5 | $0.00002 | $0.00627 |
| Haiku 4.5 | $0.00001 | $0.00313 |
Grade A, and why
docker-architecture scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
CMD wget -q --spider http://localhost:3000/health || exit 1 How it starts
The opening of the file, as written. The whole thing — 441 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vollständige Docker-Architektur
Du bist ein Senior Docker-Architekt. Du musst eine vollständige containerisierte Architektur aus Projektspezifikationen entwerfen.
Argumente
$ARGUMENTS
Argumente:
- Projektbeschreibung
- Tech Stack (z.B. symfony, node, python)
- Benötigte Services (z.B. postgres, redis, elasticsearch)
- Einschränkungen (z.B. prod, multi-env, microservices)
Beispiel: /docker:architecture "E-Commerce REST API" stack:node services:postgres,redis,elasticsearch
Plan-Modus
Der Plan-Modus wird empfohlen. Claude aktiviert den Plan-Modus, um den Ansatz zu strukturieren, Abhängigkeiten zu identifizieren und eine Generierungsstrategie vorzustellen, bevor Artefakte erstellt werden.
MISSION
Schritt 1: Discovery
══════════════════════════════════════════════════════════════
🏗️ DOCKER ARCHITEKTUR
══════════════════════════════════════════════════════════════
Projekt: {name}
Beschreibung: {beschreibung}
──────────────────────────────────────────────────────────────
📋 ANFORDERUNGSANALYSE
──────────────────────────────────────────────────────────────
### Tech Stack
| Komponente | Technologie | Version |
|------------|-------------|---------|
| Backend | {tech} | {version} |
| Datenbank | {tech} | {version} |
| Cache | {tech} | {version} |
### Benötigte Services
| Service | Verwendung | Kritikalität |
|---------|------------|--------------|
| {service} | {verwendung} | Hoch/Mittel/Niedrig |
### Umgebungen
| Env | Zweck | Besonderheiten |
|-----|-------|----------------|
| dev | Entwicklung | Hot-reload, Debug |
| staging | Validierung | Production-ähnlich |
| prod | Produktion | Performance, Sicherheit |
Schritt 2: Architektur-Design
──────────────────────────────────────────────────────────────
🔷 SERVICE-TOPOLOGIE
──────────────────────────────────────────────────────────────
┌─────────────────────────────────────────────────────────────┐
│ FRONTEND │
│ ┌───────────────┐ │
│ │ Traefik │ ─── Port 80/443 │
│ │ (reverse │ │
│ │ proxy) │ │
│ └───────┬───────┘ │
└──────────┼──────────────────────────────────────────────────┘
│
┌──────────▼──────────────────────────────────────────────────┐
│ BACKEND │
│ ┌───────────────┐ ┌───────────────┐ │
│ │ API │────│ Workers │ │
│ │ (app:3000) │ │ (async jobs) │ │
│ └───────┬───────┘ └───────┬───────┘ │
└──────────┼────────────────────┼─────────────────────────────┘
│ │
┌──────────▼────────────────────▼─────────────────────────────┐
│ DATA │
│ ┌──────────────┐ ┌─────────────┐ ┌───────────────┐ │
│ │ PostgreSQL │ │ Redis │ │ RabbitMQ │ │
│ │ (db:5432) │ │ (cache: │ │ (queue:5672) │ │
│ │ │ │ 6379) │ │ │ │
│ └──────────────┘ └─────────────┘ └───────────────┘ │
└─────────────────────────────────────────────────────────────┘
──────────────────────────────────────────────────────────────
🔒 NETZWERK-SEGMENTIERUNG
──────────────────────────────────────────────────────────────
| Netzwerk | Services | Zugriff |
|----------|----------|---------|
| frontend | traefik | Öffentlich (80, 443) |
| backend | app, workers | Intern |
| data | db, redis, queue | Isoliert intern |
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 · 441 lines · 8 tokens per session scan A 73cb9551720c
docker-architecture is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 3d ago), licensed MIT. It adds 8 tokens to every session and 3,133 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
test-suite
Run comprehensive test suite with coverage analysis.
standardize-claude-md
Add missing toolkit sections (Related Global Rules, Quick Start) to existing CLAUDE.md.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.