410-aws

410-aws is a cursor rule for Cursor from d-padmanabhan/agent-engineering-handbook. It costs 20 tokens per session (15,014 once invoked), scanned A, original, MIT.

A set of engineering rules for AWS cloud services, EKS, platform engineering, and Zero Trust security. EKS is AWS's managed service for running Kubernetes clusters, and Zero Trust means verifying every access request instead of trusting a network automatically.

In plain words
What is it for?
Use it when designing or reviewing AWS infrastructure, especially EKS platforms, Terraform or CloudFormation setups, access controls, observability, scaling, and quota planning.
Why use it?
It provides a common checklist for security, infrastructure defined in code, monitoring, costs, and AWS service limits. This helps surface design constraints before deployment.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Not installable on its own: it reads a path above its own folder, which only exists inside its repository. The line is source = "../../modules/eks-cluster".

Install

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.

Made for: Cursor.

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.

agentmods badge for 410-aws

README.md
[![agentmods](https://agentmods.dev/badge/rules/d-padmanabhan/agent-engineering-handbook/410-aws.svg)](https://agentmods.dev/rules/d-padmanabhan/agent-engineering-handbook/410-aws)
Your own site
<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>
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 15,014 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 6d ago against content hash 6470537de3ae, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

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>
rules/410-aws.mdc · 2,298 lines

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:

  1. Zero Trust: Never trust, always verify. Every request authenticated and authorized
  2. Least Privilege: Grant minimum permissions necessary; review regularly
  3. Defense in Depth: Multiple security layers; don't rely on single controls
  4. Fail Securely: Default deny; explicit allow; fail closed, not open
  5. Immutable Infrastructure: Replace, don't patch; version everything
  6. 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
}

Read the full file on GitHub · 2,298 lines

Changes

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.

  1. 6d ago First seen · 2,298 lines · 20 tokens per session scan A 6470537de3ae

Subscribe to this mod's changes

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.