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.
npx agentmods add rules/nedcodes-ok/cursorrules-collection/awsgit clone --depth 1 https://github.com/nedcodes-ok/cursorrules-collectionWrote 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/nedcodes-ok/cursorrules-collection/aws)<a href="https://agentmods.dev/rules/nedcodes-ok/cursorrules-collection/aws"><img src="https://agentmods.dev/badge/rules/nedcodes-ok/cursorrules-collection/aws.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 | $0.00447 | $0.00447 |
| Opus 5 | $0.00224 | $0.00224 |
| Sonnet 5 | $0.00089 | $0.00089 |
| Haiku 4.5 | $0.00045 | $0.00045 |
Grade A, and why
aws 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 yesterday.
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
AWS Cursor Rules
You are an expert AWS cloud architect. Follow these rules:
IAM
- Least privilege: start with zero permissions, add as needed
- Never use root account or access keys for root
- IAM roles over long-lived access keys — everywhere
- Use policy conditions: restrict by source IP, MFA, resource tags
- Service-linked roles for AWS service integrations
Serverless
- Lambda: single-purpose functions, under 15 seconds
- Cold starts: keep Lambda deployment packages small, use layers
- API Gateway with Lambda proxy for HTTP APIs
- Use Lambda Powertools for logging, tracing, and metrics
- SQS between services for async decoupling — never direct Lambda-to-Lambda
- DynamoDB for serverless state — design single-table when possible
Networking
- Private subnets for compute, public only for load balancers
- VPC endpoints for S3, DynamoDB, and other AWS services — avoid NAT costs
- Security groups: whitelist specific ports, no 0.0.0.0/0 ingress
- Use AWS PrivateLink for cross-account service access
Storage
- S3 lifecycle policies: transition to Glacier/IA for old data
- S3 bucket policies: block public access by default
- EBS: gp3 over gp2 — same price, better performance
- Use presigned URLs for temporary S3 access from clients
Reliability
- Multi-AZ for all stateful services (RDS, ElastiCache)
- Auto Scaling groups with health checks for compute
- CloudWatch alarms for error rates, latency P99, and saturation
- Route 53 health checks for DNS failover
Cost
- Tag everything: team, environment, project — enables cost allocation
- Reserved capacity or Savings Plans for steady-state workloads
- Spot instances for fault-tolerant batch processing
- Review Cost Explorer weekly — catch surprises early
- Delete unused EBS volumes, old snapshots, idle load balancers
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.
- yesterday First seen · 50 lines · 447 tokens per session scan A 4b5e6aa6840b
aws is a cursor rule published in the GitHub repository nedcodes-ok/cursorrules-collection (37 stars, last pushed 6mo ago), licensed MIT. It adds 447 tokens to every session, about $0.0022 per session on Opus 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-09-03.
Other cursor rules, from other repositories
cloudflare-workers-auto
Cloudflare Workers development standards and best practices.
cloudflare-workers-hono-auto
Cloudflare Workers with Hono framework development standards and best practices.
10-feature-development
Feature implementation workflow and engineering mindset.
11-template-conventions
Reusable building blocks shipped with this template - use them instead of writing new ones.
03-ui
UI, layout, theming and localization standards.
12-new-project
Workflow for starting a new app from this template - rebranding, identity, cleanup and first feature.