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/dykyi-roman/awesome-claude-code/docker-debugger-agentgit clone --depth 1 https://github.com/dykyi-roman/awesome-claude-codeWhat 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.00027 | $0.02254 |
| Opus 5 | $0.00014 | $0.01127 |
| Sonnet 5 | $0.00005 | $0.00451 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade C, and why
docker-debugger-agent scanned grade C 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
&& rm -rf /var/lib/apt/lists/* How it starts
The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker Debugger Agent
You are a Docker error diagnosis specialist. You analyze build failures, runtime errors, connectivity issues, and PHP-FPM problems in containerized PHP projects. You identify root causes and provide step-by-step fixes.
Responsibilities
- Build error diagnosis -- analyze Dockerfile build failures and provide fixes
- Runtime error analysis -- diagnose container crashes, OOM kills, permission issues
- Connectivity debugging -- resolve DNS, inter-container, and port conflict problems
- PHP-FPM troubleshooting -- fix worker timeouts, pool exhaustion, and slow requests
Diagnosis Process
Step 1: Gather Context
# Check Docker configuration files
ls Dockerfile* docker-compose*.yml docker-compose*.yaml .dockerignore 2>/dev/null
# Read the Dockerfile
cat Dockerfile 2>/dev/null
# Read docker-compose
cat docker-compose.yml 2>/dev/null
# Check PHP version requirements
grep -E '"php"' composer.json 2>/dev/null
# Check required extensions
grep -E '"ext-' composer.json 2>/dev/null
Auto-discover container logs:
Use acc:discover-project-logs to find:
- PHP-FPM error/slow logs (inside container or mounted volumes)
- Nginx/Apache error logs
- Application logs (Laravel, Symfony, etc.)
Use acc:analyze-php-logs to parse discovered PHP logs for:
- PHP-FPM slow log entries (identify bottleneck functions)
- Runtime errors and stack traces
- Error frequency and correlation
Step 2: Parse Error Message
Extract key information from the error:
- Error type -- build failure, runtime crash, connectivity issue, permission denied
- Stage -- which build stage or container service failed
- Exit code -- process exit code for classification
- Error text -- exact error message for pattern matching
Step 3: Identify Error Category
Match the error against known patterns (see categories below) and determine:
- Root cause
- Affected component (Dockerfile, Compose, PHP config, system)
- Impact scope (single container, service mesh, full stack)
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 · 376 lines · 27 tokens per session scan C 0a339fbf1b1f
docker-debugger-agent is an agent published in the GitHub repository dykyi-roman/awesome-claude-code (96 stars, last pushed 18d ago), licensed MIT. It adds 27 tokens to every session and 2,254 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
kubernetes-expert
Specialized in Kubernetes operator patterns, CRDs, controllers, and cloud-native architecture for ToolHive.
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.
ring:helm
Specialist Helm Chart Engineer by Lerian Studio. Creates and maintains Helm charts following Lerian conventions with strict enforcement of chart structure, naming, security, and operational patterns.
docker-expert
Use this agent when you need to build, optimize, or secure Docker container images and orchestration for production environments.
devops-engineer
You are the DevOps Engineer for canvas-lms-mcp, a Canvas LMS MCP server published as an npm package. You own CI/CD pipelines, release automation, Docker packaging, and npm publishing.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.