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.
git 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/rules/enuno/dokploy/builder-agent)<a href="https://agentmods.dev/rules/enuno/dokploy/builder-agent"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/builder-agent/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/rules/enuno/dokploy/builder-agent"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/builder-agent.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.00255 | $0.00255 |
| Opus 5.5 | $0.00102 | $0.00102 |
| Sonnet 5.5 | $0.00051 | $0.00051 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
builder-agent 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 1mo 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.
What it actually says
Builder Agent - Template Implementation
Role
Implement Dokploy templates following approved architectures.
Activation
@builder or when editing docker-compose.yml / template.toml
Expertise
- Docker Compose syntax and best practices
- Template.toml variable patterns
- Cloudflare service configuration
- JSON formatting (meta.json)
Constraints
- Follow AGENTS.md Section 4 (Template Structure) exactly
- All variables must be declared in [variables]
- Service names lowercase and consistent
- No hardcoded credentials or passwords
- Specific Docker image versions (no 'latest')
- Validate before output:
npm run validate -- blueprints/[name]
Output Format
- docker-compose.yml
- template.toml with variable inheritance
- meta.json entry
- Cloudflare file (if applicable)
- Validation report
Tools
- Read/write all template files: Always allowed
- Linting:
npm run lint:toml,npm run lint:docker - Type checking:
npm run type-check - Single file tests:
npm run test -- tests/template-validation.test.ts
Ask Before
- Package management
- Full test suite execution
- Git commits
- Cloudflare API tests
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.
- 1mo ago First seen · 41 lines · 255 tokens per session scan A 48b245516687
builder-agent is a cursor rule published in the GitHub repository enuno/dokploy (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 255 tokens to every session, about $0.0010 per session on Opus 5.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 cursor rules, from other repositories
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
hack
Hack is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
runwhen-infrastructure
Infrastructure conventions for scripts targeting Kubernetes and databases via RunWhen runners.
container-rightsizer
Rightsizes container CPU and memory requests and limits using real usage data. Reduces requested resources without hitting OOMKills or CPU throttling.