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.
npx agentmods add skills/clezcoding/awesome-coolify/coolify-incidentnpx skills add clezcoding/awesome-coolify --skill coolify-incidentgit clone --depth 1 https://github.com/clezcoding/awesome-coolifyWrote 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/skills/clezcoding/awesome-coolify/coolify-incident)<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="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 | $0.00032 | $0.00762 |
| Opus 5 | $0.00016 | $0.00381 |
| Sonnet 5 | $0.00006 | $0.00152 |
| Haiku 4.5 | $0.00003 | $0.00076 |
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 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.
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.
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: trueonly 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.
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 · 101 lines · 32 tokens per session scan A caf1ef5b2d9a
coolify-incident is a skill published in the GitHub repository clezcoding/awesome-coolify (0 stars, last pushed 4d ago), licensed MIT. It adds 32 tokens to every session and 762 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.
Other skills, from other repositories
coolify
Operate a Coolify self-hosted PaaS through the @masonator/coolify-mcp server. Use this skill whenever the user asks Claude to inspect, deploy, restart, debug, or manage anything on Coolify — including applications, databases, services, servers, projects, environments, deployments, environment variables, private keys…
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.
verify
Run this repo's verification gate — typecheck, the unit suite, the DB-backed suite. Load before running tests, pointing DATABASEURL anywhere, or reporting a unit done.
new-connector
Add or change a source connector, a REGISTRY object, or a migration. Load before writing anything in src/connectors/, src/core/schema.ts, or db/migrations/.
tube-bridge-research
Operate tube-bridge as a coherent YouTube research system: frame questions, discover sources, select subtitle tracks, classify claims, test competing hypotheses, capture timestamped evidence, build and search local corpora, and report traceable conclusions. Use for evidence-oriented YouTube research, transcript…
tomtom
TomTom Maps MCP integration — search, routing, traffic, maps, POIs, and EV via hosted endpoint.