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-vpcgit 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.00006 | $0.00911 |
| Opus 5 | $0.00003 | $0.00456 |
| Sonnet 5 | $0.00001 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
aws-vpc 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Description: AWS VPC Network Development Standards Globs: /vpc//, /network//, /infra//, /cloudformation//.yaml, /terraform//, **/.yaml
AWS VPC Development Standards
@base.mdc @typescript.mdc
VPC Architecture
- Design appropriate VPC CIDR blocks for scalability
- Implement proper subnet segmentation
- Create appropriate public/private subnet allocation
- Design proper availability zone distribution
- Implement efficient routing tables
- Create appropriate network ACLs
- Design effective security groups
- Implement proper VPC endpoints for AWS services
Subnet Design
- Implement proper CIDR allocation for subnets
- Create appropriate subnet tagging
- Design proper subnet routing
- Implement appropriate subnet groups
- Create effective subnet association with route tables
- Design subnet allocation for different resource types
- Implement proper IPv6 support when needed
- Create appropriate subnet documentation
Security Configuration
- Implement defense-in-depth security model
- Create appropriate security group rules
- Design proper network ACL rules
- Implement proper ingress/egress filtering
- Create effective security group referencing
- Design proper flow logging
- Implement appropriate VPC endpoint policies
- Create proper IAM policies for network resources
Internet Connectivity
- Implement proper Internet Gateway configuration
- Create appropriate NAT Gateway deployment
- Design effective Egress-Only Internet Gateway for IPv6
- Implement proper elastic IP management
- Create appropriate public subnet routing
- Design effective public-facing resources
- Implement proper elastic load balancer placement
- Create appropriate route table entries
VPC Connectivity
- Implement proper VPC peering when appropriate
- Create appropriate Transit Gateway configuration
- Design effective AWS PrivateLink connections
- Implement proper VPN connectivity
- Create appropriate Direct Connect integration
- Design effective hybrid networking
- Implement proper route propagation
- Create proper transitive routing solutions
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 · 143 lines · 6 tokens per session scan A 781f80df6cab
aws-vpc is a cursor rule published in the GitHub repository jimmypocock/cursor-rules (8 stars, last pushed 1y ago), licensed MIT. It adds 6 tokens to every session and 911 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.