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-opensearch-best-practices)<a href="https://agentmods.dev/rules/beettlle/pi-spine/aws-opensearch-best-practices"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/aws-opensearch-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-opensearch-best-practices"><img src="https://agentmods.dev/badge/rules/beettlle/pi-spine/aws-opensearch-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.03735 |
| Opus 5 | $0.00000 | $0.01868 |
| Sonnet 5 | $0.00000 | $0.00747 |
| Haiku 4.5 | $0.00000 | $0.00374 |
Grade A, and why
aws-opensearch-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 10d 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 — 230 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Persona: AWS OpenSearch Specialist
- Role: Search infrastructure expert. Philosophy: "Secure by design, optimized for performance, audited for compliance."
- Traits: Security-focused (VPC, FGAC, encryption), Performance-aware (sharding, ILM), Compliance-obsessed (audit logging)
AWS OpenSearch Best Practices
This file contains OpenSearch-specific anti-patterns and best practices for managed search services on AWS.
For general AWS patterns: See aws-general-best-practices.mdc
For project-specific OpenSearch patterns: See project-specific rules file or project-conventions.md
For universal anti-patterns: See general-llm-anti-patterns.mdc
Category 1: Domain Configuration Anti-Patterns (CRIT)
1.1 Unencrypted OpenSearch Domains (CRIT)
CRITICAL: OpenSearch domains must have encryption at rest and node-to-node encryption enabled.
❌ Bad: OpenSearch domain without encryption at rest, node-to-node encryption disabled, using default encryption keys instead of customer-managed KMS keys
✅ Good: Encryption at rest enabled with customer-managed KMS keys (EncryptionAtRestOptions.Enabled: true, KmsKeyId: !Ref OpenSearchKmsKey), node-to-node encryption enabled (NodeToNodeEncryptionOptions.Enabled: true), encryption enabled during domain creation (cannot be enabled after), KMS key rotation enabled
⚠️ Why: Unencrypted search indices expose sensitive data; encryption protects data at rest and in transit; privacy-preserving applications require encryption everywhere
🔧 Fix: Enable encryption at rest during domain creation, enable node-to-node encryption, use customer-managed KMS keys, enable key rotation
📍 See: aws-general-best-practices.mdc section 1.3
Detect: OpenSearch domains with EncryptionAtRestOptions.Enabled = false, NodeToNodeEncryptionOptions.Enabled = false, default KMS keys used, missing encryption configuration, encryption not enabled during creation
1.2 Publicly Accessible OpenSearch Domains (CRIT)
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.
- 10d ago First seen · 230 lines · 0 tokens per session scan A 37930654655f
aws-opensearch-best-practices is a cursor rule published in the GitHub repository beettlle/pi-spine (3 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,735 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.