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-gameliftgit clone --depth 1 https://github.com/jimmypocock/cursor-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/jimmypocock/cursor-rules/aws-gamelift)<a href="https://agentmods.dev/rules/jimmypocock/cursor-rules/aws-gamelift"><img src="https://agentmods.dev/badge/rules/jimmypocock/cursor-rules/aws-gamelift.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.00005 | $0.00858 |
| Opus 5 | $0.00003 | $0.00429 |
| Sonnet 5 | $0.00001 | $0.00172 |
| Haiku 4.5 | $0.00001 | $0.00086 |
Grade A, and why
aws-gamelift 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 4d 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 GameLift Development Standards Globs: /gamelift//, /game-server//, /matchmaking//*
AWS GameLift Development Standards
@base.mdc @typescript.mdc
GameLift Architecture
- Design proper separation between game server and client
- Implement appropriate session management
- Use proper fleet management strategies
- Design scalable matchmaking systems
- Implement proper player session tracking
- Structure game server code for reliability
- Create appropriate networking architecture
- Design for multi-region deployment when needed
Game Server Integration
- Implement the GameLift Server SDK correctly
- Initialize the server process properly
- Handle onStartGameSession callbacks appropriately
- Implement proper onProcessTerminate handling
- Create robust player session validation
- Implement proper game session logging
- Use GameLift parameters effectively
- Configure appropriate server process settings
Client Integration
- Use the GameLift Client SDK correctly
- Implement proper session placement requests
- Create appropriate matchmaking requests
- Handle session connection correctly
- Implement proper error handling for client operations
- Create resilient connection management
- Design appropriate retry strategies
- Implement proper player authentication
Fleet Management
- Design appropriate fleet configurations
- Implement proper auto-scaling policies
- Create appropriate instance type selection
- Use spot instances where appropriate
- Implement proper fleet deployment strategies
- Configure appropriate runtime configurations
- Design appropriate multi-location strategy
- Implement proper fleet monitoring
Matchmaking
- Design appropriate matchmaking configurations
- Implement proper matchmaking rules
- Create flexible rule sets for different game modes
- Design appropriate team structures
- Implement proper matchmaking event handling
- Create appropriate backfill strategies
- Design latency-based matching when appropriate
- Implement timeout handling for matchmaking
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.
- 4d ago First seen · 143 lines · 5 tokens per session scan A 7e5419e089ba
aws-gamelift 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 858 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.