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 instructions/0xtlt/coolify-mcp/agents-mdgit clone --depth 1 https://github.com/0xtlt/coolify-mcpWhat 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.00779 | $0.00779 |
| Opus 5 | $0.00390 | $0.00390 |
| Sonnet 5 | $0.00156 | $0.00156 |
| Haiku 4.5 | $0.00078 | $0.00078 |
Grade B, and why
coolify-mcp 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
- Docker is **not** part of the update script and is **not** running by default. Install Docker (Docker CE + compose plugin) and start `dockerd` yourself. In this VM the working storage driver is `fuse-overlayfs` (set in How it starts
The opening of the file, as written. The whole thing — 21 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Cursor Cloud specific instructions
coolify-mcp (npm mcp-coolify) is a stdio-based MCP server (TypeScript, ESM, pnpm) that wraps the Coolify v4.3+ REST API. It exposes 116 tools / 7 resources / 4 prompts. It has no HTTP server and opens no port — it speaks the MCP protocol over stdin/stdout and is launched by an MCP client. At runtime it needs COOLIFY_API_URL and COOLIFY_TOKEN and network access to a reachable Coolify instance; it process.exit(1)s immediately if either is missing/invalid.
Standard dev commands live in package.json scripts and README.md (pnpm run dev, pnpm start, pnpm run build, pnpm run typecheck, pnpm test/pnpm run test:unit). Lint/format is Biome; CI runs pnpm exec biome check . (no --write) — note pnpm run check uses biome check --write and will modify files. Dependencies are refreshed automatically by the startup update script (pnpm install).
Running the server / unit tests (no external services)
pnpm run test:unit,pnpm run typecheck, andpnpm exec biome check .need no Docker and no Coolify instance.- To smoke-test the server itself you must give it a live Coolify instance (see below) and drive it as an MCP client over stdio (
node dist/index.jsorpnpm start).
End-to-end / integration tests require Docker + a real Coolify (non-obvious)
GitHub Actions (.github/workflows/integration.yml) runs the integration suite against a real Coolify API — not mocks. Locally, the same path (pnpm run test:integration*) spins up a real Coolify + Postgres + Redis via docker-compose.test.yml. Unit tests in .github/workflows/ci.yml stay mocked and do not need Coolify.
- Docker is not part of the update script and is not running by default. Install Docker (Docker CE + compose plugin) and start
dockerdyourself. In this VM the working storage driver isfuse-overlayfs(set in/etc/docker/daemon.json) and iptables must beiptables-legacy; start the daemon in a tmux session withsudo dockerd. Add theubuntuuser to thedockergroup (sudo usermod -aG docker ubuntu) and, because the current shell won't pick up the new group, run docker-dependent commands viasg docker -c "...". - Compose project name must be
coolify-mcp.scripts/integration-setup.tshardcodesdocker exec coolify-mcp-coolify-1, which only exists when the Compose project is namedcoolify-mcp. Since this repo is checked out at/workspace, Compose otherwise derives the project nameworkspaceand the bootstrap step times out with "InstanceSettings not ready". Always exportCOMPOSE_PROJECT_NAME=coolify-mcpfor every integration command (setup, run, teardown), e.g.sg docker -c "COMPOSE_PROJECT_NAME=coolify-mcp pnpm run test:integration:setup". - Setup writes the minted API token and seeded resource UUIDs to
/tmp/coolify-integration-state.json; the test Coolify API is athttp://localhost:8099/api/v1. Teardown:COMPOSE_PROJECT_NAME=coolify-mcp pnpm run test:integration:teardown.
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.
- yesterday First seen · 21 lines · 779 tokens per session scan B 82487dd845e1
coolify-mcp AGENTS.md is an instructions file published in the GitHub repository 0xtlt/coolify-mcp (0 stars, last pushed 20d ago), licensed MIT. It adds 779 tokens to every session, about $0.0039 per session on Opus 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-09-01.
Other instructions, from other repositories
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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).
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
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 oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.