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-cloudformationgit 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.00844 |
| Opus 5 | $0.00003 | $0.00422 |
| Sonnet 5 | $0.00001 | $0.00169 |
| Haiku 4.5 | $0.00001 | $0.00084 |
Grade A, and why
aws-cloudformation 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 2d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description: AWS CloudFormation Development Standards Globs: **/.yaml, **/.yml, **/.json, **/.template
AWS CloudFormation Development Standards
@base.mdc
Template Structure
- Organize templates with clear sections (Parameters, Mappings, Resources, Outputs)
- Use a consistent logical resource naming convention
- Add metadata for improved template documentation
- Implement description fields for templates and resources
- Group related resources together in the template
- Keep templates modular and focused on specific components
- Use nested stacks for complex architectures
- Implement stack sets for multi-account/region deployments
Resource Definitions
- Define resources with appropriate properties
- Use intrinsic functions (Ref, GetAtt, etc.) appropriately
- Implement resource dependencies correctly
- Use DependsOn only when explicit dependencies are required
- Configure deletion policies for stateful resources
- Set up update policies for controlled updates
- Implement creation policies for resource initialization
- Use UpdateReplacePolicy to protect data during updates
Parameters
- Define parameters for configurable values
- Specify appropriate parameter types
- Set default values when applicable
- Add parameter descriptions for clarity
- Implement parameter constraints (AllowedValues, Min/Max)
- Group similar parameters using parameter groups
- Organize parameters in a logical order
- Use SSM Parameter Store references for sensitive values
Mappings
- Create mappings for environment-specific configurations
- Structure mappings with logical hierarchies
- Implement region-specific configurations via mappings
- Use mappings for instance types, AMIs, and similar variations
- Document mapping structure and usage
- Keep mappings updated with latest values
- Use FindInMap function correctly
- Implement proper fallbacks for mapping lookups
Conditions
- Create conditions for resource inclusion/exclusion
- Implement environment-specific conditions
- Use conditions for feature toggles
- Combine conditions logically when necessary
- Document condition purpose and logic
- Keep condition expressions readable
- Test condition outcomes in different scenarios
- Implement default behaviors for condition failure
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.
- 2d ago First seen · 122 lines · 5 tokens per session scan A 793a5e782d6a
aws-cloudformation 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 844 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.