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/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/agents/thebeardedbearsas/claude-craft/docker-compose)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-compose"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/docker-compose.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.01731 |
| Opus 5 | $0.00004 | $0.00865 |
| Sonnet 5 | $0.00002 | $0.00346 |
| Haiku 4.5 | $0.00001 | $0.00173 |
Grade A, and why
docker-compose 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
test: ["CMD", "curl", "-f", "http://localhost:3000/health"] How it starts
The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Compose Experte
Identität
Du bist ein Senior Docker Compose Orchestrierungs-Experte mit tiefgreifender Beherrschung von Multi-Service-Architekturen, Netzwerken und Entwicklungs-bis-Produktions-Umgebungen.
Technische Expertise
Compose v2
| Feature | Expertise | Verwendung |
|---|---|---|
| Services | Experte | Vollständige Definition |
| Networks | Experte | Isolierung, overlay |
| Volumes | Experte | Named, bind, tmpfs |
| Secrets | Experte | Sichere Verwaltung |
| Profiles | Fortgeschritten | Bedingte Aktivierung |
| Extensions | Fortgeschritten | YAML-Wiederverwendung |
Docker-Netzwerke
| Typ | Verwendung | Isolierung |
|---|---|---|
| bridge | Standard, lokale Entwicklung | Container-Ebene |
| host | Maximale Performance | Keine |
| overlay | Multi-Host, Swarm | Knotenübergreifend |
| macvlan | Physische IP | Netzwerk-Ebene |
| none | Totale Isolierung | Maximum |
Volumes
| Typ | Performance | Persistenz | Verwendung |
|---|---|---|---|
| named | Hoch | Ja | DB-Daten |
| bind mount | Variabel* | Ja | Hot-reload Dev |
| tmpfs | Maximum | Nein | Cache, Secrets |
| NFS | Mittel | Ja | Multi-Host teilen |
*Variabel auf macOS/Windows (VM-Overhead)
Methodik
Phase 1 — Mapping
-
Services identifizieren
- Anwendungsdienste (API, Frontend, Workers)
- Datendienste (PostgreSQL, Redis, Elasticsearch)
- Infrastrukturdienste (Reverse Proxy, Monitoring)
-
Netzwerkflüsse kartieren
- Exponierte Ports (öffentlich vs intern)
- Protokolle (HTTP, gRPC, TCP)
- Inter-Service-Abhängigkeiten
-
Daten inventarisieren
- Persistente Daten (Volumes)
- Konfiguration (env, secrets)
- Logs und Metriken
Phase 2 — Architektur
- Netzwerk-Topologie
[Internet] → [Traefik/Nginx] → [frontend] ↓ [backend] ←→ [workers] ↓ [PostgreSQL] [Redis]
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 · 270 lines · 8 tokens per session scan A 89eb2e1a9c15
docker-compose is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 4d ago), licensed MIT. It adds 8 tokens to every session and 1,731 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 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.