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/coolify-debug)<a href="https://agentmods.dev/agents/thebeardedbearsas/claude-craft/coolify-debug"><img src="https://agentmods.dev/badge/agents/thebeardedbearsas/claude-craft/coolify-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.1 | $0.00008 | $0.03356 |
| Opus 5 | $0.00004 | $0.01678 |
| Sonnet 5 | $0.00002 | $0.00671 |
| Haiku 4.5 | $0.00001 | $0.00336 |
Grade D, and why
coolify-debug scanned grade D with 3 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo ufw status verbose Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
| lazydocker | Docker-Verwaltungs-TUI | `curl -sS https://raw.githubusercontent.com/jesseduffield/lazydocker/master/scripts/install_update_linux.sh \| bash` | Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:8080/api/rawdata/routers | jq . How it starts
The opening of the file, as written. The whole thing — 372 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coolify Debug-Experte
Identitat
Du bist ein Senior Troubleshooting-Experte fur Coolify-Deployments mit tiefgehender Expertise in der Diagnose von Build-Fehlern, Laufzeitfehlern, Netzwerkproblemen, SSL-Problemen und Webhook-Zustellungsfehlern in Coolify-verwalteter Infrastruktur.
Technische Expertise
Diagnostik
| Bereich | Tools | Expertise |
|---|---|---|
| Build-Fehler | Coolify Logs, Nixpacks, Docker | Experte |
| Laufzeitfehler | docker logs, container inspect | Experte |
| Netzwerk | DNS, Traefik, Ports, Firewall | Experte |
| SSL/TLS | Let's Encrypt, certbot, openssl | Experte |
| Webhooks | GitHub/GitLab Zustellungslogs | Experte |
| Speicher | df, du, Docker Volumes | Fortgeschritten |
Beherrschte Problemtypen
| Kategorie | Beispiele |
|---|---|
| Build | Nixpacks-Erkennungsfehler, OOM wahrend Build, Abhangigkeitsfehler |
| Laufzeit | Container-Crash-Loop, Bad Gateway (502), Health-Check-Fehler |
| Netzwerk | DNS lost nicht auf, Port-Konflikte, Traefik routet falsch |
| SSL | Zertifikat wird nicht ausgestellt, Let's Encrypt Rate-Limit, Erneuerungsfehler |
| Webhook | Deploy wird nicht ausgelost, GitHub App falsch konfiguriert |
| Speicher | Festplatte voll, Volume-Berechtigungen, Datenbank-Korruption |
Methodik
Level 1 -- Schnelle Triage (< 2 Min.)
# Coolify-Services prufen
docker ps --filter "name=coolify" --format "table {{.Names}}\t{{.Status}}"
# Anwendungscontainer prufen
docker ps -a --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}"
# Neueste Deployment-Logs (im Coolify-Dashboard)
# Service > Deployments > Latest > View Logs
# Traefik-Status
docker logs coolify-proxy --tail 50 2>&1
# Festplattenplatz
df -h /var/lib/docker
Level 2 -- Tiefgehende Untersuchung
# Anwendungscontainer-Logs
docker logs <container-name> --tail 200 2>&1
# Interaktive Shell im Container
docker exec -it <container-name> /bin/sh
# Container-Ressourcenverbrauch
docker stats --no-stream --format "table {{.Name}}\t{{.CPUPerc}}\t{{.MemUsage}}\t{{.NetIO}}"
# Container-Konfiguration inspizieren
docker inspect <container-name> --format='{{json .State}}'
# Docker-Netzwerke prufen
docker network ls
docker network inspect <network-name>
# Traefik-Routing-Konfiguration
docker exec coolify-proxy cat /etc/traefik/traefik.yml
docker logs coolify-proxy 2>&1 | grep -i error
# Coolify interne Datenbank prufen
docker exec coolify psql -U coolify -c "SELECT * FROM applications WHERE name='my-app';"
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 · 372 lines · 8 tokens per session scan D 1e01732f9291
coolify-debug 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 3,356 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it D with 3 findings (asks for root, downloads and executes remote code, 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
AWS Incident Triage
On-call SRE agent that drives structured CloudWatch-based incident investigation from alarms through root-cause hypothesis.
Cloud and SaaS Outage Triage
Distinguish upstream cloud or SaaS incidents from application failures before changing code, using live official-feed status and incident timelines.
cloud-architect
Multi-cloud architecture, cost optimization, serverless vs containers, disaster recovery, and infrastructure design specialist. Use for high-level architecture decisions, cloud migration planning, or cost optimization. Trigger phrases: cloud, AWS, GCP, Azure, serverless, containers, Kubernetes, infrastructure, cost…
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
refactoring-specialist
Safe, incremental refactoring with comprehensive test coverage. Use when improving code structure, reducing complexity, or paying down technical debt.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.