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-rds-best-practices)<a href="https://agentmods.dev/rules/beettlle/pi-spine/aws-rds-best-practices"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/aws-rds-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-rds-best-practices"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/aws-rds-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.03199 |
| Opus 5 | $0.00000 | $0.01599 |
| Sonnet 5 | $0.00000 | $0.00640 |
| Haiku 4.5 | $0.00000 | $0.00320 |
Grade A, and why
aws-rds-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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: AWS RDS Database Specialist
- Role: Database infrastructure expert. Philosophy: "Security first, performance optimized, backups automated."
- Traits: Security-focused (encryption, private subnets), Performance-aware (connection pooling, indexing), Reliability-obsessed (backups, Multi-AZ)
AWS RDS Best Practices
This file contains RDS PostgreSQL-specific anti-patterns and best practices for managed database services on AWS.
For general AWS patterns: See aws-general-best-practices.mdc
For project-specific RDS patterns: See project-specific rules file or project-conventions.md
For universal anti-patterns: See general-llm-anti-patterns.mdc
Category 1: Database Configuration Anti-Patterns (CRIT)
1.1 Unencrypted RDS Instances (CRIT)
CRITICAL: RDS instances must have encryption at rest enabled. This is non-negotiable for privacy-preserving applications.
❌ Bad: RDS instance without encryption at rest (StorageEncrypted: false), using default encryption keys instead of customer-managed KMS keys
✅ Good: Enable encryption at rest with customer-managed KMS keys (StorageEncrypted: true, KmsKeyId: !Ref DatabaseKmsKey), encryption enabled during instance creation (cannot be enabled after), KMS key rotation enabled, encrypted automated backups
⚠️ Why: Unencrypted databases expose sensitive data if storage is compromised; encryption at rest required for compliance; customer-managed keys provide control
🔧 Fix: Enable encryption at rest during RDS creation, use customer-managed KMS keys, enable key rotation, ensure backups are encrypted
📍 See: aws-general-best-practices.mdc section 1.3
Detect: RDS instances with StorageEncrypted = false, instances without KMS key configuration, unencrypted database snapshots, default KMS keys used, KMS key rotation disabled
1.2 Publicly Accessible RDS Instances (CRIT)
CRITICAL: RDS instances must not be publicly accessible. They must be in private subnets with no public IP.
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 · 202 lines · 0 tokens per session scan A 47153328c7ea
aws-rds-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 3,199 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
netlify-database
Zero-config Postgres for Netlify apps via @netlify/database — querying data from Functions/Edge Functions, writing schema migrations, setting up Drizzle ORM, local dev with netlify dev, database branches for deploy previews, and migrating an existing Postgres project onto Netlify. Use when adding a database, building…
rds-proxy
RDS Proxy patterns - PostgreSQL connection pooling, Prisma integration, transaction handling, read replicas.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
postgresql
PostgreSQL production rules. Safe migrations, parameterized queries, TIMESTAMPTZ, proper indexing strategy.