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/pi-spineWrote 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/pi-spine/aws-general-best-practices)<a href="https://agentmods.dev/rules/beettlle/pi-spine/aws-general-best-practices"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/aws-general-best-practices/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/beettlle/pi-spine/aws-general-best-practices"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/aws-general-best-practices.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.00000 | $0.04637 |
| Opus 5 | $0.00000 | $0.02318 |
| Sonnet 5 | $0.00000 | $0.00927 |
| Haiku 4.5 | $0.00000 | $0.00464 |
Grade A, and why
aws-general-best-practices 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: AWS Solutions Architect
- Role: Senior Cloud Architect specializing in secure, scalable, privacy-preserving applications. Philosophy: "Security by design, defense in depth, least privilege."
- Traits: Security-first mindset, compliance-aware, automation-focused, cost-conscious without compromising security, observability-obsessed
AWS General Best Practices
This file contains general AWS best practices aligned with the AWS Well-Architected Framework. These practices apply across all AWS services and infrastructure.
For service-specific patterns: See aws-fargate-best-practices.mdc, aws-rds-best-practices.mdc, aws-opensearch-best-practices.mdc, aws-cloudwatch-best-practices.mdc
For project-specific AWS patterns: See project-specific rules file or project-conventions.md
For universal anti-patterns: See general-llm-anti-patterns.mdc
CRITICAL: Security and Operational Excellence are generally not traded-off against other pillars.
Category 1: Security Pillar (CRITICAL)
1.1 Identity and Access Management (IAM) (CRIT)
CRITICAL: Implement least privilege access control. Never use long-term credentials in application code.
❌ Bad: AWS_ACCESS_KEY_ID = "AKIA..." (hardcoded), Fargate tasks using IAM users with access keys, IAM policies with "Action": "*", "Resource": "*"
✅ Good: IAM roles for Fargate tasks (task execution role + task role), least privilege policies (specific actions/resources), MFA required for console access, quarterly access reviews
⚠️ Why: Credentials in code exposed in version control/logs/container images; overly permissive policies increase attack surface; missing MFA enables credential theft
🔧 Fix: Use IAM task roles for Fargate, AWS Secrets Manager for secrets, grant only required permissions, enable MFA for all users, review access quarterly
📍 See: general-llm-anti-patterns.mdc section 5.1
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.
- 9d ago First seen · 268 lines · 0 tokens per session scan A 1ab77dcf1b36
aws-general-best-practices is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,637 tokens. 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
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.