What is coolify-incident?

An incident-response workflow for Coolify, a platform used to deploy and run applications. It helps investigate an application that is down or behaving poorly by examining logs and attempting recovery.

Use it to resolve an application, inspect runtime and deployment logs, follow supported live logs, restart the application, and request approval before destructive recovery steps.

It provides an ordered way to identify runtime or deployment problems and starts with a restart before considering more destructive actions.

coolify-incident — Skill for Claude Code and Codex by clezcoding

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.

Any agent

npx skills add clezcoding/awesome-coolify --skill coolify-incident

Clone the repo

git clone --depth 1 https://github.com/clezcoding/awesome-coolify

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/clezcoding/awesome-coolify/coolify-incident/github.svg)](https://agentmods.dev/skills/clezcoding/awesome-coolify/coolify-incident)

Your own site

<a href="https://agentmods.dev/skills/clezcoding/awesome-coolify/coolify-incident"><img src="https://agentmods.dev/badge/skills/clezcoding/awesome-coolify/coolify-incident/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/clezcoding/awesome-coolify/coolify-incident"><img src="https://agentmods.dev/badge/skills/clezcoding/awesome-coolify/coolify-incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 762 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00032	$0.00762
Opus 5.5	$0.00013	$0.00305
Sonnet 5.5	$0.00006	$0.00152
Haiku 4.5	$0.00003	$0.00076

Measured 1mo ago against content hash caf1ef5b2d9a, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

coolify-incident 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 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.

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-incident/SKILL.md · 101 lines

How it starts

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

Coolify Incident

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

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

MCP prompt analog: incident (src/mcp/prompts.ts)

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

Incident response workflow

Resolve application UUID — from args, .coolify/manifest.json, or ask the user.
Check capabilities:
```
system({ action: "version" })
```

Triage and tail application logs:

diagnose({ action: "logs", mode: "full", uuid: "<uuid>" })

Follow a live application symptom when supported:

application({ action: "logs", uuid: "<uuid>", follow: true })

On build or deploy suspicion, inspect deployment logs:
```
deployment({ action: "logs", deployment_uuid: "<deployment-uuid>" })
```
Coolify 4.1.x supports application runtime and deployment logs. Service/database logs are unavailable because their REST endpoints do not exist.

Attempt least-destructive recovery — restart:

application({ action: "restart", uuid: "<uuid>" })

If restart is insufficient — ask the human before destructive actions. Preview emergency redeploy:
```
emergency({ action: "redeploy_project", project_uuid: "<project-uuid>", confirm: false })
```
Retry with confirm: true only after explicit human approval.
Report incident status, actions taken, and recommended follow-up.

Deploy watch after recovery

When redeploying, use coolify-deploy watch-primary flow:

application({ action: "deploy", uuid: "<uuid>", wait: false })
deployment({ action: "watch", deployment_uuid: "<deployment_uuid>", timeout: 300 })

On COOLIFY_WATCH_TIMEOUT, re-call deployment.watch with the same deployment_uuid.

Read the full file on GitHub · 101 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.

1mo ago First seen · 101 lines · 32 tokens per session scan A caf1ef5b2d9a

Subscribe to this mod's changes

coolify-incident is a skill published in the GitHub repository clezcoding/awesome-coolify (0 stars, last pushed 5d ago), licensed MIT. It adds 32 tokens to every session and 762 once invoked, about $0.0001 per session on Opus 5.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.

Debugging DevOps and cloud TypeScript coolify mcp model-context-protocol self-hosted

debugging-executions

Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…

n8n-io/n8n · 86 tokens

n8n-docs-assistant

Answers n8n product, setup, credential, node, hosting, API, and usage questions from current n8n docs. Use when the user asks how to configure, set up, troubleshoot, or understand n8n behavior, especially credential setup questions — including which OAuth scopes or permissions a provider app needs.

n8n-io/n8n · 71 tokens

runtime-diagnostics

Investigate Pioneer Gateway or desktop CPU, memory, slow work, queues, and runtime stalls using process metrics, local snapshots, bounded native profiles, and exact release symbols. Use for Pioneer performance diagnosis and interpreting its diagnostic artifacts.

pioneerdotai/pioneer · 49 tokens

coolify-incident