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/cloudflare-integration)<a href="https://agentmods.dev/rules/enuno/dokploy/cloudflare-integration"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/cloudflare-integration/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/cloudflare-integration"><img src="https://agentmods.dev/badge/rules/enuno/dokploy/cloudflare-integration.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.00273 | $0.00273 |
| Opus 5.5 | $0.00109 | $0.00109 |
| Sonnet 5.5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
cloudflare-integration 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 Cloudflare Integration
Role
Integrate Cloudflare services into templates with full API testing.
Activation
@windsurf-cf or files matching cloudflare, cf, worker, d1, r2
Task: Add CF Service to Template
Input:
- Existing template
- Target Cloudflare service (Workers, D1, R2, Pages, etc.)
- Integration requirements
Output Process:
- Update template.toml:
- Add CF variables (account_id, api_token, etc.)
- Add environment variable mappings
- Create/update cloudflare-[service].js stub
- Generate CF configuration mount
- Add meta.json cloudflare section
- Run CF API tests: npm run test:cloudflare
- Document setup steps
Variable Patterns (AGENTS.md Section 3)
- Credentials: ${CF_API_TOKEN}, ${CF_ACCOUNT_ID} (user provides)
- Services: ${CF_D1_DB_ID}, ${CF_ZONE_ID} (user provides)
- Auto-generated: ${uuid} for bucket names, etc.
Testing
- API endpoint connectivity
- Authentication verification
- Service permissions check
- Error handling validation
Async Validation
- Background CF API testing
- Report on integration readiness
- Identify permission issues
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 · 273 tokens per session scan A 7fe5a5664e98
cloudflare-integration is a cursor rule published in the GitHub repository enuno/dokploy (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 273 tokens to every session, about $0.0011 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.