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-setup)<a href="https://agentmods.dev/commands/thebeardedbearsas/claude-craft/coolify-setup"><img src="https://agentmods.dev/badge/commands/thebeardedbearsas/claude-craft/coolify-setup.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.01746 |
| Opus 5 | $0.00003 | $0.00873 |
| Sonnet 5 | $0.00001 | $0.00349 |
| Haiku 4.5 | $0.00001 | $0.00175 |
Grade C, and why
coolify-setup scanned grade C 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 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.
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.
- [ ] Coolify installiert: curl -fsSL https://cdn.coolify.io/install.sh | bash Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- [ ] Coolify installiert: curl -fsSL https://cdn.coolify.io/install.sh | bash How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Coolify-Einrichtung
Du bist ein Coolify-Deployment-Spezialist. Du musst das Projekt analysieren und fur das Deployment auf einer Coolify Self-Hosted-PaaS-Instanz vorbereiten.
Argumente
$ARGUMENTS
Argumente:
- Projektbeschreibung oder Pfad
- (Optional) Ziel-Build-Pack: nixpacks, dockerfile, compose
- (Optional) Benotigte Services: postgres, redis, mysql, mongodb
Beispiel: /coolify:setup "Node.js API mit PostgreSQL und Redis" oder /coolify:setup . buildpack:dockerfile services:postgres,redis
Plan-Modus
Der Plan-Modus ist obligatorisch. Vor der Ausführung aktiviert Claude den Plan-Modus, um betroffenen Code zu analysieren, einen Implementierungsplan vorzuschlagen und auf Ihre Validierung zu warten, bevor Änderungen vorgenommen werden.
MISSION
Schritt 1: Projekt-Stack analysieren
# Projekttyp erkennen
ls -la package.json composer.json requirements.txt go.mod Cargo.toml Gemfile *.csproj 2>/dev/null
# Vorhandene Docker-Dateien prufen
ls -la Dockerfile* docker-compose*.yml .dockerignore nixpacks.toml 2>/dev/null
# Umgebungskonfiguration prufen
ls -la .env .env.example .env.local 2>/dev/null
# Services aus dem Code identifizieren
grep -r "DATABASE_URL\|REDIS_URL\|MONGODB_URI\|MYSQL_" .env* 2>/dev/null
══════════════════════════════════════════════════════════════
COOLIFY PROJEKT-EINRICHTUNG
══════════════════════════════════════════════════════════════
Projekt: {name}
Pfad: {pfad}
──────────────────────────────────────────────────────────────
STACK-ERKENNUNG
──────────────────────────────────────────────────────────────
| Komponente | Erkannt | Version |
|------------|---------|---------|
| Sprache | {sprache} | {version} |
| Framework | {framework} | {version} |
| Paketmanager | {npm/yarn/pnpm/composer/pip} | {version} |
| Service | Erkannt | Quelle |
|---------|---------|--------|
| {datenbank} | {ja/nein} | {Umgebungsvariable / Konfigurationsdatei} |
| {cache} | {ja/nein} | {Umgebungsvariable / Konfigurationsdatei} |
| {queue} | {ja/nein} | {Umgebungsvariable / Konfigurationsdatei} |
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 · 227 lines · 6 tokens per session scan C 1bb6c2b116b4
coolify-setup is a command published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 4d ago), licensed MIT. It adds 6 tokens to every session and 1,746 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 2 findings (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 commands, from other repositories
datadog
Set up and troubleshoot Datadog — Agent deployment on Kubernetes, APM instrumentation, Log Management, Monitors, Dashboards, SLOs, Synthetic tests, and live incident investigation using the Datadog MCP server. Covers Terraform-managed Datadog resources.
aws-profile
AWS profile management for MCP servers — discover profiles across SSO, Granted, and assumed-role chains, check credential TTL, switch profiles across VS Code and Claude Code MCP configs, and scan AWS Organization accounts.
migrating-fabric-trial-capacities
Migrate workspaces from trial capacity to production capacity.
firebase-publish
Create or reuse a Firebase project, configure Hosting, and deploy the current static site. Never deletes.
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.