Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/d-padmanabhan/agent-engineering-handbook/410-aws)<a href="https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/410-aws"><img src="https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/410-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.1 | $0.00020 | $0.15014 |
| Opus 5 | $0.00010 | $0.07507 |
| Sonnet 5 | $0.00004 | $0.03003 |
| Haiku 4.5 | $0.00002 | $0.01501 |
Grade A, and why
410-aws 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 6d 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.
curl -v https://<service-dns-name> How it starts
The opening of the file, as written. The whole thing — 2,298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AWS Engineering Ruleset
Goal: Build secure, scalable, maintainable AWS infrastructure following best practices for Platform Engineering, Zero Trust, and EKS.
[!IMPORTANT] MAKE SURE TO READ AWS WELL-ARCHITECTED FRAMEWORK BEFORE ANSWERING. Use the AWS Well-Architected Framework as the baseline for recommendations: https://docs.aws.amazon.com/wellarchitected/latest/framework/welcome.html
[!IMPORTANT] Treat AWS Service Quotas as a first-class design constraint (regional/account limits). Validate quotas early for the services you depend on, request quota increases before rollout, and bake the limits into scaling and architecture decisions: https://docs.aws.amazon.com/servicequotas/latest/userguide/intro.html
AWS Engineering Philosophy
Guiding Principles:
- Security First: Zero Trust architecture, least privilege, defense in depth, encryption everywhere
- Infrastructure as Code: All infrastructure defined in code (Terraform, CloudFormation, CDK); no manual changes
- Observability: Comprehensive logging, metrics, and tracing; monitor everything
- Cost Optimization: Right-sizing, reserved instances, spot instances; measure and optimize continuously
- Disaster Recovery: Multi-region, backups, failover strategies; test regularly
- Automation: Automate everything possible; reduce toil, increase reliability
- Scalability: Design for growth; horizontal scaling preferred over vertical
Core Tenets:
- Zero Trust: Never trust, always verify. Every request authenticated and authorized
- Least Privilege: Grant minimum permissions necessary; review regularly
- Defense in Depth: Multiple security layers; don't rely on single controls
- Fail Securely: Default deny; explicit allow; fail closed, not open
- Immutable Infrastructure: Replace, don't patch; version everything
- Idempotency: Operations should be safe to repeat; infrastructure as code ensures this
Applying AWS Philosophy:
# BAD: Trusting network boundaries
resource "aws_security_group" "app" {
ingress {
from_port = 443
to_port = 443
protocol = "tcp"
cidr_blocks = ["0.0.0.0/0"] # Trusting all IPs
}
}
# GOOD: Zero Trust - explicit allowlist
resource "aws_security_group" "app" {
ingress {
from_port = 443
to_port = 443
protocol = "tcp"
security_groups = [aws_security_group.lb.id] # Only from load balancer
}
}
# BAD: Overly permissive IAM
resource "aws_iam_role_policy" "app" {
policy = jsonencode({
Statement = [{
Effect = "Allow"
Action = "s3:*" # Too broad
Resource = "*"
}]
})
}
# GOOD: Least privilege
resource "aws_iam_role_policy" "app" {
policy = jsonencode({
Statement = [{
Effect = "Allow"
Action = [
"s3:GetObject",
"s3:ListBucket"
]
Resource = [
aws_s3_bucket.data.arn,
"${aws_s3_bucket.data.arn}/*"
]
}]
})
}
# BAD: Manual changes (not idempotent)
# Manual: Created RDS instance via console
# GOOD: Infrastructure as Code (idempotent)
resource "aws_db_instance" "main" {
identifier = "app-db"
engine = "postgres"
instance_class = "db.t3.medium"
# ... Terraform manages state
}
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.
- 6d ago First seen · 2,298 lines · 20 tokens per session scan A 6470537de3ae
410-aws is a cursor rule published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 6d ago), licensed MIT. It adds 20 tokens to every session and 15,014 once invoked, about $0.0001 per session on Opus 5. 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-30.
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.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
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.