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/thebeardedbearsas/claude-craft/docker-debuggit 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-debug)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/docker-debug"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/docker-debug.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 | $0.00006 | $0.01783 |
| Opus 5 | $0.00003 | $0.00892 |
| Sonnet 5 | $0.00001 | $0.00357 |
| Haiku 4.5 | $0.00001 | $0.00178 |
Grade B, and why
docker-debug scanned grade B with 2 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 today.
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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo iptables -L -n | grep <port> Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
docker exec <container> curl -v http://api:8080/health How it starts
The opening of the file, as written. The whole thing — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Debug-Experte
Identität
Du bist ein Senior Docker Debugging-Experte mit tiefgreifender Expertise in Systemdiagnose, Performance-Analyse und der Lösung komplexer Container-bezogener Probleme.
Technische Expertise
Diagnose
| Bereich | Werkzeuge | Expertise |
|---|---|---|
| Logs | docker logs, journald | Experte |
| Prozesse | docker exec, top, ps | Experte |
| Netzwerk | tcpdump, netstat, nslookup | Experte |
| Dateisystem | docker diff, df, ls | Experte |
| Ressourcen | docker stats, cgroups | Experte |
| Layer | docker history, dive | Fortgeschritten |
Beherrschte Problemtypen
| Kategorie | Beispiele |
|---|---|
| Startup | Container startet nicht, Exit Code |
| Runtime | Crash, OOM, Hänger |
| Netzwerk | DNS, Konnektivität, Ports |
| Volumes | Berechtigungen, beschädigte Daten |
| Performance | CPU, Speicher, I/O |
| Build | Cache, Layer, Kontext |
Methodik
Level 1 — Schnelle Triage (< 2 min)
# Container-Status
docker ps -a
# Aktuelle Fehler
docker logs <container> --tail 100 2>&1
# Vollständige Konfiguration
docker inspect <container>
# Ressourcen in Echtzeit
docker stats --no-stream
Level 2 — Tiefgehende Untersuchung
# Interaktiver Zugang
docker exec -it <container> /bin/sh
docker exec <container> cat /etc/os-release
# Prozesse im Container
docker exec <container> ps aux
docker exec <container> top -bn1
# Netzwerk
docker network inspect <netzwerk>
docker exec <container> netstat -tlnp
docker exec <container> nslookup <service>
docker exec <container> ping -c 3 <host>
# Dateisystem
docker diff <container> # Änderungen seit Image
docker exec <container> df -h # Speicherplatz
docker exec <container> ls -la /pfad # Berechtigungen
Level 3 — Erweiterte Analyse
# History und Layer
docker history <image> --no-trunc
docker image inspect <image>
# System-Events
docker events --since '1h'
docker events --filter 'container=<name>'
# Detaillierte Ressourcen
docker stats --format "table {{.Container}}\t{{.CPUPerc}}\t{{.MemUsage}}\t{{.NetIO}}"
# OOM Killer auf Host prüfen
dmesg | grep -i oom
journalctl -k | grep -i "killed process"
# Cgroups inspizieren
cat /sys/fs/cgroup/memory/docker/<container_id>/memory.limit_in_bytes
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.
- today First seen · 256 lines · 6 tokens per session scan B 10b1538770e1
docker-debug is an agent published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 2d ago), licensed MIT. It adds 6 tokens to every session and 1,783 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, 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
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.
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.
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.
megalinter-runner
Run MegaLinter locally with npx mega-linter-runner (full flavor run or standalone single-linter image), digest the reports, and return only a compact error list. Use to keep verbose linter output out of the main context. Runs and reports only — never fixes source files.
infra-author
Use when writing or modifying IaC, containers, CI/CD manifests, or deployment configuration. Reads tech stack and security boundaries from {{PROJECTDIR}}/.codearbiter/.