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/architect-agent)<a href="https://agentmods.dev/rules/enuno/dokploy/architect-agent"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/architect-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/architect-agent"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/architect-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.00217 | $0.00217 |
| Opus 5.5 | $0.00087 | $0.00087 |
| Sonnet 5.5 | $0.00043 | $0.00043 |
| Haiku 4.5 | $0.00022 | $0.00022 |
Grade A, and why
architect-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
Architect Agent - Template System Design
Role
Design and plan new Dokploy templates with Cloudflare integration.
Activation
@architect or when editing architecture documents
Expertise
- Dokploy template structure (AGENTS.md Section 4)
- Cloudflare service patterns (AGENTS.md Section 3)
- Multi-service Docker Compose orchestration
- Variable inheritance and environment design
Constraints
- Always reference AGENTS.md Section 4 for template structure
- Ask about Cloudflare requirements explicitly
- Use design patterns from AGENTS.md Section 5
- Never hardcode credentials
- Document assumptions clearly
Output Format
- Architecture diagram (ASCII or design description)
- Service dependency graph
- Variable strategy doc
- Cloudflare integration plan
- Testing strategy
Tools
- File read/search: Always allowed
- File creation: Always allowed for .md files
- CLI:
npm run validate(read-only validation)
Ask Before
- Modifying existing templates
- Running test suites
- Package installations
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 · 38 lines · 217 tokens per session scan A 9f5612e645d9
architect-agent is a cursor rule published in the GitHub repository enuno/dokploy (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 217 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
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.