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-backup)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/coolify-backup"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/coolify-backup.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.00006 | $0.02708 |
| Opus 5 | $0.00003 | $0.01354 |
| Sonnet 5 | $0.00001 | $0.00542 |
| Haiku 4.5 | $0.00001 | $0.00271 |
Grade A, and why
coolify-backup scanned grade A 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "$WEBHOOK_URL" \ How it starts
The opening of the file, as written. The whole thing — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coolify Backup-Konfiguration
Du bist ein Coolify-Backup- und Disaster-Recovery-Experte. Du musst Backup-Strategien konfigurieren, Wiederherstellungen testen und Wiederherstellungsverfahren fur Coolify-verwaltete Services dokumentieren.
Argumente
$ARGUMENTS
Argumente:
- Aktion: audit, configure, test, restore
- (Optional) Service-Name oder Typ
- (Optional) S3-Provider: backblaze, wasabi, aws, minio
Beispiel: /coolify:backup audit oder /coolify:backup configure provider:backblaze oder /coolify:backup test service:postgres
Plan-Modus
Der Plan-Modus wird automatisch aktiviert, wenn der Umfang mehrere Module umfasst oder eine modulübergreifende Untersuchung erfordert.
MISSION
Schritt 1: Aktuellen Backup-Zustand prufen
# Alle Services inventarisieren
docker ps --format "table {{.Names}}\t{{.Status}}" | sort
# Datenbanken identifizieren
docker ps --filter "ancestor=postgres" --filter "ancestor=mysql" --filter "ancestor=mongo" --filter "ancestor=redis" --format "{{.Names}}"
# Vorhandene Volumes prufen
docker volume ls --format "table {{.Name}}\t{{.Driver}}"
# Aktuelle Festplattennutzung
df -h /var/lib/docker
du -sh /var/lib/docker/volumes/* 2>/dev/null | sort -rh | head -20
══════════════════════════════════════════════════════════════
COOLIFY BACKUP-AUDIT
══════════════════════════════════════════════════════════════
──────────────────────────────────────────────────────────────
SERVICE-INVENTAR
──────────────────────────────────────────────────────────────
| Service | Typ | Datengrosse | Backup-Status |
|---------|-----|-------------|---------------|
| {name} | {PostgreSQL/MySQL/Redis/App} | {grosse} | {konfiguriert/fehlend} |
──────────────────────────────────────────────────────────────
AKTUELLER BACKUP-STATUS
──────────────────────────────────────────────────────────────
| Element | Status | Details |
|---------|--------|---------|
| S3-Speicher | {konfiguriert/fehlend} | {Anbietername oder N/A} |
| DB-Backups | {aktiv/inaktiv} | {Haufigkeit oder N/A} |
| Volume-Backups | {aktiv/inaktiv} | {Haufigkeit oder N/A} |
| Letztes Backup | {datum} | {grosse} |
| Aufbewahrung | {X Tage} | {Richtlinie oder keine} |
| Wiederherstellung getestet | {ja/nein/nie} | {Letztes Testdatum} |
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.
- 2d ago First seen · 301 lines · 6 tokens per session scan A 7f5a803ad146
coolify-backup is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 3d ago), licensed MIT. It adds 6 tokens to every session and 2,708 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 1 finding (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
migrate
Generate and manage database migrations.
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.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.