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-lambdagit 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.00892 |
| Opus 5 | $0.00003 | $0.00446 |
| Sonnet 5 | $0.00001 | $0.00178 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
aws-lambda 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 yesterday.
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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description: AWS Lambda Function Best Practices Globs: /lambda//.ts, /functions//.ts, /src//.ts, /lambda//.py, /functions//.py, /src//.py
AWS Lambda Development Standards
@base.mdc @typescript.mdc
Lambda Function Design
- Follow single responsibility principle for each Lambda function
- Keep functions focused on one specific task or domain operation
- Separate business logic from infrastructure concerns
- Create pure functions where possible for easier testing
- Implement idempotent functions to handle retries safely
- Design functions to be stateless
- Avoid long-running processes; break them into smaller steps
Handler Structure
- Keep handlers thin, delegating to service or business logic layers
- Validate input parameters early in the function
- Return properly structured responses
- Add custom context to errors for better debugging
- Follow these layers in Lambda implementation:
- Handler layer (entry point)
- Service layer (business logic)
- Data access layer (repository pattern)
- External service integrations
Performance Optimization
- Initialize SDK clients and database connections outside the handler
- Cache static assets and reference data between invocations
- Implement connection pooling for database access
- Utilize provisioned concurrency for latency-sensitive functions
- Set appropriate memory allocation based on function needs
- Use environment variables for configuration
- Implement backoff strategies for external service calls
- Leverage AWS SDK client reuse whenever possible
Cold Start Mitigation
- Keep function code and dependencies lightweight
- Use AWS Lambda Layers for large dependencies
- Use provisioned concurrency for critical paths
- Implement warmup mechanisms for important functions
- Consider using NodeJS or native runtime for faster cold starts
- Choose appropriate memory settings to balance CPU/memory needs
- Set reasonable function timeouts
Error Handling
- Implement comprehensive error handling and logging
- Add context information to errors
- Use structured logging with correlation IDs
- Distinguish between client errors (4xx) and server errors (5xx)
- Use try/catch blocks with specific error types
- Handle retries with exponential backoff
- Consider implementing circuit breakers for external services
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.
- yesterday First seen · 114 lines · 5 tokens per session scan A 93ce70ed7edd
aws-lambda 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 892 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
app_feature_first_architecture
Feature-first architecture is a design pattern that organizes code by business features rather than technical layers. This approach promotes better maintainability, scalability, and team collaboration by keeping related functionality together and reducing coupling between different parts of the application.
mobile
Rules for mobile development (Swift/iOS, Kotlin Android, React Native, Flutter).
java-kotlin
Rules applied when working in Java or Kotlin files (incl. Android).
90-devops-deployment
Docker, CI/CD, AWS, Vercel, and VPS deployment rules.
00-global-architect
Global default behavior for the entire repository.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.