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/beettlle/CursorRulesWrote 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/beettlle/cursorrules/aws-fargate-best-practices)<a href="https://agentmods.dev/rules/beettlle/cursorrules/aws-fargate-best-practices"><img src="https://agentmods.dev/badge/rules/beettlle/cursorrules/aws-fargate-best-practices.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.1 | $0.00000 | $0.03085 |
| Opus 5 | $0.00000 | $0.01543 |
| Sonnet 5 | $0.00000 | $0.00617 |
| Haiku 4.5 | $0.00000 | $0.00309 |
Grade A, and why
aws-fargate-best-practices scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
✅ Good: Fargate task health checks configured (`"healthCheck": {"command": ["CMD-SHELL", "curl -f http://localhost:8888/health || exit 1"], "interval": 30, "timeout": 5, "retries": 3, "startPeriod": 60}`), application he The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 7d ago First seen · 207 lines · 0 tokens per session scan A da5d913fef8c
aws-fargate-best-practices is a cursor rule published in the GitHub repository beettlle/CursorRules (2 stars, last pushed 23d ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 3,085 tokens. A static security scan graded it A with 1 finding (makes network calls). 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
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
kubernetes
This guide defines definitive best practices for writing, organizing, and securing Kubernetes manifests and Operators, ensuring maintainable, performant, and reliable cloud-native deployments.
kubernetes
Kubernetes and OpenShift workload generation rules — security defaults, resource limits, probes.
build-deployment
Build, CMake, and Docker deployment.
kubernetes-helm
Kubernetes and Helm best practices including resource management, security, chart organization, and deployment patterns.
deployment
Rails Deployment with Kamal.