dokploy blueprints.instructions.md

Project instructions for developing enuno/Dokploy blueprints, which package Docker services with configuration, an icon, and setup documentation.

In plain words
What is it for?
Use them when creating or modifying files in a blueprints directory, especially docker-compose.yml, template.toml, icons, and README files.
Why use it?
They define the required files and rules for image versions, storage, networking, ports, variables, secrets, and Cloudflare integration so templates follow one consistent structure.

Instructions file for GitHub Copilot

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 instructions/enuno/dokploy/blueprints
Clone the repo
git clone --depth 1 https://github.com/enuno/dokploy

Made for: GitHub Copilot.

Per session 766 This file is loaded in full into every session.
When invoked 766 The same file — it is already loaded in full.
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.00766 $0.00766
Opus 5 $0.00383 $0.00383
Sonnet 5 $0.00153 $0.00153
Haiku 4.5 $0.00077 $0.00077

Measured 2d ago against content hash 179aef65ea22, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dokploy blueprints.instructions.md 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 2d 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.

.github/instructions/blueprints.instructions.md · 97 lines

How it starts

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

Blueprint Development Instructions

When creating or modifying files in blueprints/:

File Structure

Each blueprint requires:

  • docker-compose.yml - Container orchestration
  • template.toml - Dokploy configuration
  • [app-name].svg - Logo/icon
  • README.md - Setup and usage instructions

Docker Compose Rules

  • Version: 3.8+ only
  • Images: Pinned tags (query Docker Hub for latest stable version)
    image: grafana/grafana:10.2.0  # ✅ Good
    image: grafana/grafana:latest  # ❌ Bad
    
  • Restart policy: unless-stopped on all services
  • Volumes: Named volumes only, no bind mounts
  • Ports: Never expose ports (Traefik handles routing)
  • Networks: Don't define (Dokploy manages networking)

template.toml Rules

  • Variables section: Declare all variables in [variables] first
  • serviceName: MUST match compose service name exactly
  • Helpers: Use Dokploy helpers for secrets
    • ${password:32} - 32-byte random password
    • ${domain} - Auto-generated domain
    • ${uuid} - RFC4122 UUID
    • ${base64:32} - 32-byte base64 string
  • Environment variables: Reference user-provided vars like ${CF_API_TOKEN}

Cloudflare Integration

If template uses Cloudflare services:

  • Use ${CF_ACCOUNT_ID}, ${CF_API_TOKEN}, etc. (never hardcode)
  • Add cloudflare object to meta.json entry
  • Document CF prerequisites in README.md
  • Include example worker/D1/R2 configuration files

meta.json Entry

Append entry with:

{
  "id": "app-name",
  "name": "Application Name",
  "version": "1.0.0",
  "description": "Brief description",
  "logo": "app-name.svg",
  "links": {
    "github": "https://github.com/org/repo",
    "website": "https://example.com",
    "docs": "https://docs.example.com"
  },
  "tags": ["category", "feature"],
  "cloudflare": {
    "supported_services": ["Workers", "D1"],
    "optional": true,
    "documentation": "docs/templates/app-cloudflare.md"
  }
}

Validation (must pass before PR)

# Syntax check
docker compose -f blueprints/[name]/docker-compose.yml config

# Template validation
npm run validate -- blueprints/[name]

# Full test suite
npm run test:coverage

Read the full file on GitHub · 97 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. 2d ago First seen · 97 lines · 766 tokens per session scan A 179aef65ea22

Subscribe to this mod's changes

dokploy blueprints.instructions.md is an instructions file published in the GitHub repository enuno/dokploy (2 stars, last pushed 21d ago), licensed Apache-2.0. It adds 766 tokens to every session, about $0.0038 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 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.

github/spec-kit · 7,104 tokens

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

microsoft/vscode · 6,785 tokens

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.

openai/codex · 5,182 tokens

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.

langchain-ai/langchain · 4,345 tokens

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

microsoft/vscode · 5,001 tokens

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.

vercel/next.js · 7,296 tokens