05-aws-rosa-context

A set of rules for code that interacts with AWS and ROSA, Red Hat's managed OpenShift service on Amazon Web Services.

In plain words
What is it for?
Use it when changing AWS-facing code or setup guidance involving identity, networking, regions, quotas, credentials, or ROSA deployment types.
Why use it?
It keeps cloud-related changes aligned with official behavior and helps avoid unsafe handling of credentials, configuration, and platform differences.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/openshift/rosa/05-aws-rosa-context
Clone the repo
git clone --depth 1 https://github.com/openshift/rosa

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 209 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00209
Opus 5 $0.00000 $0.00105
Sonnet 5 $0.00000 $0.00042
Haiku 4.5 $0.00000 $0.00021

Measured 2d ago against content hash 991d80072e9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

05-aws-rosa-context 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.

.cursor/rules/05-aws-rosa-context.mdc · 16 lines

What it actually says

AWS And ROSA Context

  • Treat official ROSA and AWS documentation as the truth source for architecture, prerequisites, and user-facing setup behavior.
  • Before changing AWS-facing code, verify whether the behavior differs between ROSA with HCP and ROSA classic.
  • Cross-check STS, IAM, OIDC, VPC, subnet, PrivateLink, quota, region, and credential assumptions against the official docs linked from AGENTS.md.
  • Do not hardcode credentials or add logging that exposes tokens, keys, or secret values.
  • Do not silently bump AWS SDK or related dependency versions; if a bump is required, call it out explicitly and verify downstream impact.
  • Prefer existing helpers and AWS client wrappers already used in the surrounding package.
  • Be careful with user-facing setup or troubleshooting text: make sure AWS CLI install, profiles, and config guidance match current AWS documentation.
Changes

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.

  1. 2d ago First seen · 16 lines · 0 tokens per session scan A 991d80072e9e

Subscribe to this mod's changes

05-aws-rosa-context is a cursor rule published in the GitHub repository openshift/rosa (103 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 209 tokens. 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-30.