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/enuno/dokploy/dokploy-environment-confignpx skills add enuno/dokploy --skill dokploy-environment-configgit clone --depth 1 https://github.com/enuno/dokployWrote 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/enuno/dokploy/dokploy-environment-config)<a href="https://agentmods.dev/skills/enuno/dokploy/dokploy-environment-config"><img src="https://agentmods.dev/badge/skills/enuno/dokploy/dokploy-environment-config.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.00028 | $0.02932 |
| Opus 5 | $0.00014 | $0.01466 |
| Sonnet 5 | $0.00006 | $0.00586 |
| Haiku 4.5 | $0.00003 | $0.00293 |
Grade A, and why
dokploy-environment-config 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 4d 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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dokploy Environment Configuration
When to Use This Skill
- When defining environment variables for Dokploy templates
- When deciding between required and optional variables
- When configuring database connection strings
- When organizing environment sections
- When user asks about "environment variables" or "secrets"
When NOT to Use This Skill
- For template.toml variables (use dokploy-template-toml)
- For Traefik configuration (use dokploy-traefik-routing)
Prerequisites
- Application documentation (required env vars)
- Understanding of docker-compose variable syntax
- Knowledge of sensitive vs non-sensitive data
Core Patterns
Pattern 1: Required Variables (:? syntax)
Variables that MUST be set - deployment fails without them:
environment:
DOMAIN: ${DOMAIN:?Set your domain (e.g., example.com)}
DATABASE_PASSWORD: ${DATABASE_PASSWORD:?Set a secure database password}
SECRET_KEY: ${SECRET_KEY:?Set a secret key for session encryption}
Syntax: ${VAR_NAME:?Error message}
- If VAR_NAME is unset or empty, shows error message and fails
- Use for: domains, passwords, API keys, secrets
Pattern 2: Optional Variables (:- syntax)
Variables with sensible defaults:
environment:
LOG_LEVEL: ${LOG_LEVEL:-info}
WORKERS: ${WORKERS:-4}
CACHE_TTL: ${CACHE_TTL:-3600}
DEBUG: ${DEBUG:-false}
Syntax: ${VAR_NAME:-default_value}
- If VAR_NAME is unset or empty, uses default_value
- Use for: tuning parameters, feature flags, optional settings
Pattern 3: Internal Constants
Values that shouldn't change:
environment:
# Database host is always the service name
PGHOST: postgres
REDIS_HOST: redis
# Ports are fixed in the container
PGPORT: "5432"
REDIS_PORT: "6379"
Pattern 4: Computed Values
Variables derived from other variables:
environment:
APP_URL: https://${DOMAIN}
DATABASE_URL: postgresql://${DB_USER}:${DB_PASS}@postgres:5432/${DB_NAME}
MONGO_URL: mongodb://mongodb:27017/${MONGO_DB:-appdb}
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.
- 4d ago First seen · 424 lines · 28 tokens per session scan A 02d89fd1e447
dokploy-environment-config is a skill published in the GitHub repository enuno/dokploy (2 stars, last pushed 23d ago), licensed Apache-2.0. It adds 28 tokens to every session and 2,932 once invoked, about $0.0001 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
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…
rule
Skill "rule" from x-cmd/x-cmd, covering rule — rules to rule, 核心命令, 规则文件格式, 示例 and 验证规则文件格式.
cve
Look up CVE records via x cve — cached, zero-API-key, daily xz TSV. Load for cve, vulnerability id, kev, epss, nvd, cvelist, or security advisory.
azmon-mirroredcatalogs-operations-cli
Brings Azure Monitor, Application Insights, and Log Analytics telemetry into Fabric as Eventhouse external delta tables and correlates it with business data. Use to onboard observability data, judge whether latency or availability affected revenue, or build a Real-Time dashboard and Operations Agent over it.
atmos-auth
Authentication and identity management: providers (SSO/SAML/OIDC/GCP/Atmos Pro), identities, keyring, identity chaining, login/exec/shell/console, and github/sts for private GitHub access.
terraform-search-import
Discover existing cloud resources using Terraform Search queries and bulk import them into Terraform management. Use when bringing unmanaged infrastructure under Terraform control, auditing cloud resources, or migrating to IaC.