coolify-setup

A setup workflow for connecting a project to Coolify, a platform for deploying applications on your own servers. It checks prerequisites and links projects, environments, and servers.

In plain words
What is it for?
Use it to run setup preflight checks, provision or link Coolify resources, and resume setup after GitHub access has been configured.
Why use it?
It reduces setup mistakes and pauses safely when human GitHub authentication is required.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/clezcoding/awesome-coolify/coolify-setup
Any agent
npx skills add clezcoding/awesome-coolify --skill coolify-setup
Clone the repo
git clone --depth 1 https://github.com/clezcoding/awesome-coolify

Made for: Claude Code, Codex.

Per session 33 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,537 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00033 $0.01537
Opus 5 $0.00016 $0.00768
Sonnet 5 $0.00007 $0.00307
Haiku 4.5 $0.00003 $0.00154

Measured yesterday against content hash e705cdc998df, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

coolify-setup scanned grade A with 0 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 yesterday.

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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/coolify-setup/SKILL.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Coolify Setup

Install this skill pack (Cursor, Claude Code, Codex):

npx skills add clezcoding/awesome-coolify -a cursor -a claude-code -a codex

MCP prompt analog: new-project (src/mcp/prompts.ts) — primary entry is MCP setup tool per D-01.

Related skills: coolify-deploy · coolify-diagnose · coolify-incident

MCP setup tool

Primary entry: MCP setup tool (setupActionsCatalog):

  • preflight() — verify GitHub CLI presence and auth (headless-safe)
  • wire(mode, ...) — provision or link Coolify resources
  • resume(mode?, ...) — re-run preflight after human gh auth

Safety: optional instance routing · no auto-push git by default · gh soft-pause (no in-tool poll)

Workflow

  1. Preflight — call setup({ action: "preflight" }).
  2. On COOLIFY_SETUP_PAUSED — stop for human action:
    • Install gh if missing: cli.github.com
    • Run gh auth login (or set GH_TOKEN / GITHUB_TOKEN for headless)
    • Do not poll or sleep inside the agent loop waiting for auth.
  3. Resume — after auth succeeds, call setup({ action: "resume", ... }) with the same wire params you will use for step 4.
  4. Wire — call setup({ action: "wire", mode: "greenfield" | "link-existing", ... }).

Modes

Mode Use when
greenfield Create new Coolify project/environment and provision via recipe
link-existing Attach workspace to an existing Coolify project/server

Optional flags (default off)

Pass explicitly only when needed:

  • include_domains — attach domains after wire (greenfield, or link-existing with application_uuid)
  • set_env — sync environment variables after wire (greenfield, or link-existing with application_uuid). When enabled, pass exactly one of env_file (local .env path) or env_content (inline .env text) — no workspace auto-detect. Application resources only (not one-click services).
  • deploy_and_watch — trigger deploy and bounded deployment.watch after wire (greenfield, or link-existing with application_uuid)
  • push — on greenfield only; default false omits gh --push. Set push: true to push after repo create.

Read the full file on GitHub · 141 lines

Changes

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.

  1. yesterday First seen · 141 lines · 33 tokens per session scan A e705cdc998df

Subscribe to this mod's changes

coolify-setup is a skill published in the GitHub repository clezcoding/awesome-coolify (0 stars, last pushed 3d ago), licensed MIT. It adds 33 tokens to every session and 1,537 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

artifact

Share documents, images, and PDFs with a human as persistent links via the Artifacts MCP server. Use when the user asks to publish or share an artifact, document, diagram, generated image, or PDF with a link.

dbtlr/artifacts · 47 tokens

coss

Helps implement coss UI components correctly. Use when building UIs with coss primitives (buttons, dialogs, selects, forms, menus, tabs, inputs, toasts, etc.), migrating from shadcn/Radix to coss/Base UI, composing trigger-based overlays, or troubleshooting coss component behavior. Covers imports, accessibility…

usekaneo/kaneo · 80 tokens

post-build-flow

Handles workflow verification and setup after build-workflow succeeds, or when the message contains workflow-verification-follow-up or workflow-setup-required. Load after direct builds, when verificationReadiness requires action, or on orchestrator verify/setup follow-up turns.

n8n-io/n8n · 53 tokens

n8n:content-design

Product content designer for UI copy. Use when writing, reviewing, or auditing user-facing text: button labels, error messages, tooltips, empty states, modal copy, placeholder text, confirmation dialogs, onboarding flows, or i18n strings. Also use when the user says /copy, /content, or /ux-copy.

n8n-io/n8n · 73 tokens

n8n:human-like-code-review

Reviews a GitHub pull request like a thoughtful human reviewer and writes the feedback to a markdown file. Prioritizes context, architecture fit, solution complexity, bugs, security edge cases, and missing tests. Use when given a PR URL to review, or when the user says /human-like-code-review.

n8n-io/n8n · 70 tokens

n8n:node-add-oauth

Add OAuth2 credential support to an existing n8n node — creates the credential file, updates the node, adds tests, and keeps the CLI constant in sync. Use when the user says /node-add-oauth.

n8n-io/n8n · 53 tokens