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/commands/thebeardedbearsas/claude-craft/docker-debug)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/docker-debug"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/docker-debug/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/commands/thebeardedbearsas/claude-craft/docker-debug"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/docker-debug.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.00002 | $0.01305 |
| Opus 5.5 | $0.00001 | $0.00522 |
| Sonnet 5.5 | $0.00000 | $0.00261 |
| Haiku 4.5 | $0.00000 | $0.00130 |
Grade A, and why
docker-debug 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Diagnose
Du bist ein Docker Debugging-Experte. Du musst Container-bezogene Probleme diagnostizieren und lösen.
Argumente
$ARGUMENTS
Argumente:
- Symptom oder Fehlermeldung
- (Optional) Container-Name
- (Optional) Kontext (dev/prod)
Beispiel: /docker:debug "Container beendet mit Code 137" oder /docker:debug app "Connection refused"
Plan-Modus
Der Plan-Modus wird automatisch aktiviert, wenn der Umfang mehrere Module umfasst oder eine modulübergreifende Untersuchung erfordert.
MISSION
Schritt 1: Informationen sammeln
# Container-Status
docker ps -a
# Aktuelle Logs
docker logs <container> --tail 100 2>&1
# Vollständige Inspektion
docker inspect <container>
# Ressourcen
docker stats --no-stream
Schritt 2: Problem identifizieren
══════════════════════════════════════════════════════════════
🔍 DOCKER DIAGNOSE
══════════════════════════════════════════════════════════════
Container: {name}
Image: {image}
Status: {running|exited|restarting}
Laufzeit: {dauer}
──────────────────────────────────────────────────────────────
🚨 GEMELDETES SYMPTOM
──────────────────────────────────────────────────────────────
{Problembeschreibung}
──────────────────────────────────────────────────────────────
📋 ANALYSE
──────────────────────────────────────────────────────────────
Schritt 3: Entscheidungsbäume
Container startet nicht
| Exit Code | Bedeutung | Aktionen |
|---|---|---|
| 0 | Normal beendet | CMD/ENTRYPOINT prüfen |
| 1 | Anwendungsfehler | Logs analysieren |
| 126 | Berechtigung verweigert | Berechtigungen prüfen |
| 127 | Befehl nicht gefunden | PATH und Binary prüfen |
| 137 | SIGKILL (OOM oder Stop) | Speicher prüfen |
| 139 | SIGSEGV | Code debuggen |
# Exit Code prüfen
docker inspect --format='{{.State.ExitCode}}' <container>
# OOM prüfen
docker inspect --format='{{.State.OOMKilled}}' <container>
# Detaillierte Logs
docker logs <container> 2>&1
Netzwerkprobleme
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 · 232 lines · 2 tokens per session scan A 9e315c936814
docker-debug is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed yesterday), licensed MIT. It adds 2 tokens to every session and 1,305 once invoked, about $0.0000 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-10-30.
Other commands, from other repositories
bootstrap
Verify and repair the Claude Code toolkit installation.
health-check
Run diagnostics on Claude Code toolkit configuration and status.
flow-nexus-sandbox
E2B sandbox management for isolated code execution.
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.