Coolify is a self-hosted platform for managing servers and deploying applications, databases, static sites, and other services on hardware controlled by the user. Developers and teams use it as an alternative to hosted application platforms such as Heroku, Netlify, and Vercel, while the catalogue entries help coding agents operate Coolify.
Borrowing it
Nothing to install: this file belongs to coollabsio/coolify. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/coollabsio/coolify/main/AGENTS.mdgit clone --depth 1 https://github.com/coollabsio/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/instructions/coollabsio/coolify/agents-md)<a href="https://agentmods.dev/instructions/coollabsio/coolify/agents-md"><img src="https://agentmods.dev/badge/instructions/coollabsio/coolify/agents-md/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.
<a href="https://agentmods.dev/instructions/coollabsio/coolify/agents-md"><img src="https://agentmods.dev/badge/instructions/coollabsio/coolify/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.09049 | $0.09049 |
| Opus 5.5 | $0.03620 | $0.03620 |
| Sonnet 5.5 | $0.01810 | $0.01810 |
| Haiku 4.5 | $0.00905 | $0.00905 |
Grade B, and why
coolify AGENTS.md scanned grade B 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- When adding remote shell commands, account for servers using non-root SSH users: commands pass through `parseCommandsByLineForSudo()`, so test pipelines, redirects, substitutions, and `sh -c`/`bash -c` scripts with the How it starts
The opening of the file, as written. The whole thing — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to agentic coding tools when working with code in this repository.
Project Overview
Coolify is an open-source, self-hostable PaaS (alternative to Heroku/Netlify/Vercel). It manages servers, applications, databases, and services via SSH. Built with Laravel 12 (using Laravel 10 file structure), Livewire 3, and Tailwind CSS v4.
Design Reference
For UI/UX design specifications, principles, and visual standards, consult the local DESIGN.md. It is the source of truth for frontend design work in this repository.
Development Environment
Docker Compose-based dev setup with services: coolify (app, which also runs Reverb WebSockets and the terminal server), postgres, redis, vite, testing-host, mailpit, minio.
# One dev instance per git branch (containers, volumes, VMs named after the branch)
./scripts/dev start [qemu-profile] # localhost VM: KVM (Linux, /dev/kvm + root/sudo) or Lima (macOS, limactl), else testing-host
./scripts/dev stop # stop containers and VMs; data is kept for the next start
./scripts/dev run # start + follow logs, stop on exit (Jean run script)
./scripts/dev urls # all instances, URLs, ports, and checkouts
./scripts/dev exec php artisan migrate # run a command in this branch's Coolify container
./scripts/dev destroy <name> # delete containers, volumes, VMs, and the port slot
./scripts/dev teardown # destroy this worktree's instance (Jean teardown before worktree deletion)
# Compose: docker-compose.dev-multi.yml Env + slots: <main checkout>/.dev-instances/ (gitignored)
# Legacy fixed-name stack (not used by scripts/dev)
docker compose -f docker-compose.yml -f docker-compose.dev.yml up -d
The main checkout serves its branch at localhost:8000 (Reverb 6001, terminal 6002, db 5432, redis 6379, vite 5173). Worktrees get a port block at 20000 + slot*10 (app +0, Reverb +1, terminal +2, db +3, redis +4, vite +5). Each instance has its own libvirt network coolify-dev-<slot> (10.221.<slot>.0/24) and VMs coolify-dev-<branch>--<profile>; VMs are reused, use php artisan dev:qemu <profile> --fresh to rebuild one. On macOS with Lima >= 2.0 (brew install lima), the localhost VM is the Lima instance coolify-dev-<slot>-<profile> (same profiles, users, and SSH key); Coolify reaches it through Lima's forwarded SSH port on host.docker.internal, and only guest ports 80/443 are forwarded to the Mac. Rebuild it with limactl delete -f <vm>. Force it with COOLIFY_DEV_SERVER_BACKEND=lima. To pass the host NVIDIA GPU through to the KVM localhost VM (ubuntu-root only), start with COOLIFY_DEV_GPU=1 ./scripts/dev start (or php artisan dev:qemu ubuntu-root --as-localhost --gpu). This attaches every PCI function of the GPU, gives the VM 4 GiB, stops nvidia-persistenced on the host, and installs the NVIDIA driver and container toolkit in the VM. The host cannot use the GPU while the VM runs. Remove it with --fresh without --gpu. If APP_URL in .env is a *.ts.net host, the browser ports are published with tailscale serve. Set COOLIFY_DEV_INSTANCE=<name> to run another instance from the same checkout.
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 Changed · +19 lines · +427 tokens per session aeb72a172024
- 5d ago Changed · +1 lines · +39 tokens per session b277e157c1aa
- 6d ago Changed · +115 tokens per session 141c5f4f1a37
- 9d ago Changed · +16 lines · +618 tokens per session af1b96c1245a
- 12d ago Changed · +16 lines · +346 tokens per session d9de4bb617dd
- 23d ago Changed · +45 tokens per session 43b413af6e51
- 25d ago Changed · +6 lines · +270 tokens per session 7c25a3da9a0a
- 29d ago Changed · +4 lines · +373 tokens per session a73ff05d081c
- 1mo ago Changed · -3 lines · -10 tokens per session 5e30d34f701d
- 1mo ago First seen · 440 lines · 6,826 tokens per session scan B 31774457c0ff
coolify AGENTS.md is an instructions file published in the GitHub repository coollabsio/coolify (65,330 stars, last pushed today), licensed Apache-2.0. It adds 9,049 tokens to every session, about $0.0362 per session on Opus 5.5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.