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/jimmypocock/cursor-rules/aws-eventbridgegit clone --depth 1 https://github.com/jimmypocock/cursor-rulesWhat 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.00005 | $0.00832 |
| Opus 5 | $0.00003 | $0.00416 |
| Sonnet 5 | $0.00001 | $0.00166 |
| Haiku 4.5 | $0.00001 | $0.00083 |
Grade A, and why
aws-eventbridge 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.
How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description: AWS EventBridge Development Standards Globs: /events//, /eventbridge//, /event-driven//, /serverless//
AWS EventBridge Development Standards
@base.mdc @typescript.mdc
Event Design
- Design standardized event schemas
- Implement proper event versioning
- Create appropriate detail field structures
- Design consistent event source naming
- Implement proper event metadata
- Create appropriate correlation IDs for tracing
- Design effective event filtering patterns
- Implement proper event documentation
Event Bus Architecture
- Design appropriate event bus organization
- Implement proper default vs. custom event buses
- Create appropriate cross-account event routing
- Design effective event archiving strategies
- Implement proper event replay capabilities
- Create appropriate event pattern matching
- Design efficient event routing patterns
- Implement proper event bus security
Rule Configuration
- Design effective event pattern rules
- Implement proper rule targets
- Create appropriate rule prioritization
- Design consistent rule naming conventions
- Implement proper rule documentation
- Create appropriate rule tagging
- Design efficient rule evaluation
- Implement proper rule testing
Event Processing
- Implement idempotent event processors
- Create appropriate event validation
- Design effective event transformation
- Implement proper error handling
- Create appropriate dead-letter queues
- Design efficient batching strategies
- Implement proper event logging
- Create appropriate processing metrics
Integration Patterns
- Design effective Lambda integration
- Implement proper SQS queue integration
- Create appropriate SNS topic targets
- Design effective Step Functions integration
- Implement proper Kinesis stream targets
- Create appropriate API destination integration
- Design effective cross-service event patterns
- Implement proper third-party integrations
Schema Registry
- Implement proper schema definitions
- Create appropriate schema versions
- Design effective schema discovery
- Implement proper code binding generation
- Create appropriate schema validation
- Design proper schema evolution
- Implement schema documentation
- Create appropriate schema sharing
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 · 143 lines · 5 tokens per session scan A 79f41727f690
aws-eventbridge is a cursor rule published in the GitHub repository jimmypocock/cursor-rules (8 stars, last pushed 1y ago), licensed MIT. It adds 5 tokens to every session and 832 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
00-global-architect
Global default behavior for the entire repository.
35-api-contracts
API versioning, contracts, and schema evolution rules.
45-environment-config
Environment configuration and secrets management rules.
50-rag-system
Retrieval-augmented generation rules.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.