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/template-builder)<a href="https://agentmods.dev/rules/enuno/dokploy/template-builder"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/template-builder/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/template-builder"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/template-builder.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.00229 | $0.00229 |
| Opus 5.5 | $0.00092 | $0.00092 |
| Sonnet 5.5 | $0.00046 | $0.00046 |
| Haiku 4.5 | $0.00023 | $0.00023 |
Grade A, and why
template-builder 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
Windsurf Template Builder
Role
Build complete Dokploy templates with validation and testing.
Activation
@windsurf-build or editing blueprints/ files
Task: Create Template from Architecture
Input:
- Architecture document (from @architect)
- Service specifications
- Cloudflare integration requirements
Output Process:
- Create docker-compose.yml
- Create template.toml with variable inheritance
- Create meta.json entry
- Run validation: npm run validate -- blueprints/[name]
- Run tests: npm run test -- tests/template-validation.test.ts
- Report status and any fixes needed
Constraints (from AGENTS.md)
- Service names: lowercase
- Image versions: specific (no 'latest')
- Variables: declared before use
- Credentials: environment variable refs only
- No hardcoded passwords or tokens
Post-Generation
- Validate passes: npm run validate
- Tests pass: >80% coverage
- Ready for staging: staging URL provided
Async Tasks
- Background validation on save
- Test suite runs incrementally
- Notifications on completion
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 · 40 lines · 229 tokens per session scan A 243208b75f49
template-builder is a cursor rule published in the GitHub repository enuno/dokploy (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 229 tokens to every session, about $0.0009 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
docker-persistence
A set of rules for keeping application data after Docker containers are replaced, managing service start and stop behavior, and running regression tests. Docker is a tool for packaging and running applications in containers.
docker-compose-non-unit-testing
Use Docker Compose workflows for integration, stress, E2E, and DB/Redis-backed tests.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.
313-frameworks-spring-boot-local-testing
Best practices for local testing in Spring Boot applications using spring-boot-docker-compose for seamless integration with external services like databases, message queues, and caches.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
fuzzing
Fuzzing setup and guidelines for skia-rs.