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.
npx agentmods add rules/goranerhartic/cursor-development-rules/sns-eventsgit clone --depth 1 https://github.com/GoranErhartic/cursor-development-rulesWrote 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/goranerhartic/cursor-development-rules/sns-events)<a href="https://agentmods.dev/rules/goranerhartic/cursor-development-rules/sns-events"><img src="https://agentmods.dev/badge/rules/goranerhartic/cursor-development-rules/sns-events.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 | $0.00029 | $0.00411 |
| Opus 5 | $0.00015 | $0.00205 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
sns-events 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 3d 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.
What it actually says
SNS Event Publishing Patterns
Event Envelope
- Use consistent envelope:
eventId,eventType,aggregateId,aggregateType,version,timestamp,correlationId,causationId?,metadata: { source, userId?, traceId? },payload - Generate
eventId(e.g. UUID); propagatecorrelationIdfrom context or create new
Publishing
- Client:
@aws-sdk/client-sns;PublishCommandwithTopicArn,Message(JSON string),MessageAttributesfor filtering (e.g.eventTypeas String) - Message: Stringify envelope; set
MessageGroupIdfor FIFO topics - Attributes: Use for SQS subscription filter policies; type String/Number/Binary
Receiving (SNS → Lambda)
- Event:
SNSEvent;event.Records[].Sns.Messageis stringified payload; parse JSON; validate; process - Idempotency: Required when processing can be duplicated; use idempotency key from eventId or aggregateId+eventType
CDK
- Create topic with
new sns.Topic(); subscribe queue withtopic.addSubscription(new subscriptions.SqsSubscription(queue)); filter policy on subscription for attribute-based filtering - FIFO: Topic and queue must be FIFO; MessageGroupId required
Conventions
- Always use envelope; include correlationId; use message attributes for filtering; idempotent processing; log publish/consume with correlationId
Anti-Patterns
- Raw payload without envelope; no correlationId; no idempotency for consumers; publishing without error handling
See also: sqs-processing.mdc, eventbridge.mdc, idempotency.mdc
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.
- 3d ago First seen · 37 lines · 29 tokens per session scan A 7f9161de5281
sns-events is a cursor rule published in the GitHub repository GoranErhartic/cursor-development-rules (19 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 411 once invoked, about $0.0001 per session on Opus 5. 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-30.
Other cursor rules, from other repositories
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.