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/coolify-debug)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/coolify-debug"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/coolify-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/coolify-debug"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/coolify-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.00006 | $0.01924 |
| Opus 5.5 | $0.00002 | $0.00770 |
| Sonnet 5.5 | $0.00001 | $0.00385 |
| Haiku 4.5 | $0.00001 | $0.00192 |
Grade B, and why
coolify-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 1mo 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 Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -o /dev/null -w "%{http_code}" https://{domain} How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coolify-Diagnose
Du bist ein Coolify-Debugging-Experte. Du musst Deployment- und Laufzeitprobleme auf Coolify Self-Hosted-PaaS diagnostizieren und beheben.
Argumente
$ARGUMENTS
Argumente:
- Symptom oder Fehlermeldung
- (Optional) Service-Name
- (Optional) Kontext: build, runtime, networking, ssl
Beispiel: /coolify:debug "502 Bad Gateway auf app.example.com" oder /coolify:debug "Build fehlschlagt mit OOM" service:api
Plan-Modus
Der Plan-Modus wird automatisch aktiviert, wenn der Umfang mehrere Module umfasst oder eine modulübergreifende Untersuchung erfordert.
MISSION
Schritt 1: Symptome erfassen
══════════════════════════════════════════════════════════════
COOLIFY-DIAGNOSE
══════════════════════════════════════════════════════════════
Service: {name}
Typ: {Application / Database / Docker Compose}
Build Pack: {Nixpacks / Dockerfile / Compose}
──────────────────────────────────────────────────────────────
GEMELDETES SYMPTOM
──────────────────────────────────────────────────────────────
{Problembeschreibung}
### Symptom-Klassifizierung
| Kategorie | Wahrscheinlichkeit |
|-----------|-------------------|
| Build-Fehler | {Hoch/Mittel/Niedrig} |
| Laufzeitfehler | {Hoch/Mittel/Niedrig} |
| Netzwerk | {Hoch/Mittel/Niedrig} |
| SSL/TLS | {Hoch/Mittel/Niedrig} |
| Webhook/Git | {Hoch/Mittel/Niedrig} |
| Speicher | {Hoch/Mittel/Niedrig} |
Schritt 2: Deployment-Status und Logs prufen
# 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}}"
# Anwendungslogs (vom Coolify-Dashboard oder CLI)
docker logs <container-name> --tail 200 2>&1
# Traefik-Proxy-Logs
docker logs coolify-proxy --tail 100 2>&1 | grep -i "error\|warn"
# Systemressourcen
free -h
df -h /var/lib/docker
──────────────────────────────────────────────────────────────
DEPLOYMENT-STATUS
──────────────────────────────────────────────────────────────
| Prufung | Ergebnis | Details |
|---------|----------|---------|
| Container-Zustand | {running/exited/restarting} | {Laufzeit oder Exit-Code} |
| Health Check | {healthy/unhealthy/none} | {Letztes Prufungsergebnis} |
| Traefik-Route | {aktiv/fehlend} | {Domain-Routing-Status} |
| Letztes Deploy | {Erfolg/Fehlgeschlagen} | {Zeitstempel} |
| Ressourcen | {OK/Warnung} | CPU: {%}, RAM: {verwendet/gesamt} |
| Festplatte | {OK/Warnung} | {verwendet/gesamt} ({Prozent}) |
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.
- 1mo ago First seen · 253 lines · 6 tokens per session scan B efbf161b6cc7
coolify-debug is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (107 stars, last pushed 5d ago), licensed MIT. It adds 6 tokens to every session and 1,924 once invoked, about $0.0000 per session on Opus 5.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 commands, from other repositories
bootstrap
Verify and repair the Claude Code toolkit installation.
health-check
Run diagnostics on Claude Code toolkit configuration and status.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.