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-bedrockgit 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-bedrock)<a href="https://agentmods.dev/rules/jimmypocock/cursor-rules/aws-bedrock"><img src="https://agentmods.dev/badge/rules/jimmypocock/cursor-rules/aws-bedrock.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.00894 |
| Opus 5 | $0.00003 | $0.00447 |
| Sonnet 5 | $0.00001 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
aws-bedrock 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 Bedrock Development Standards Globs: /bedrock//, /ai//, /llm//, /agents//
AWS Bedrock Development Standards
@base.mdc @typescript.mdc
Foundational Model Integration
- Select appropriate foundation models for specific use cases
- Implement proper model version management
- Use appropriate prompt engineering techniques
- Create proper model parameter configurations
- Implement contextual prompting strategies
- Design proper model fallback mechanisms
- Apply proper model evaluation metrics
- Implement cost-efficient model usage patterns
API Integration
- Use the Bedrock API client correctly
- Implement proper authentication and authorization
- Create appropriate error handling for API calls
- Design resilient retry strategies
- Implement proper request throttling
- Create appropriate request batching
- Design efficient request/response handling
- Implement proper logging for model interactions
Prompt Engineering
- Design clear, specific prompts for models
- Implement proper prompt templating systems
- Create appropriate context windows
- Design effective few-shot prompting examples
- Implement proper system prompts
- Create appropriate task-specific prompt patterns
- Design prompt validation mechanisms
- Implement proper prompt versioning
Response Processing
- Implement proper response parsing
- Create appropriate response validation
- Design proper error handling for model outputs
- Implement content filtering when needed
- Create appropriate response transformation
- Design fallback mechanisms for poor responses
- Implement appropriate response caching
- Create proper logging for model responses
Bedrock Agents
- Configure appropriate agent actions and APIs
- Implement proper agent orchestration
- Create appropriate action group definitions
- Design proper agent response handling
- Implement appropriate agent prompts
- Create secure API schemas for agent integration
- Design appropriate agent knowledge bases
- Implement proper agent versioning and deployment
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 cbaf50bde7cd
aws-bedrock 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 894 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
50-rag-system
Retrieval-augmented generation rules.
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
data-science
Rules for data science, ML, and Jupyter notebook work.
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.