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 skills/openshift/rosa/rosa-aws-contextnpx skills add openshift/rosa --skill rosa-aws-contextgit clone --depth 1 https://github.com/openshift/rosaWrote 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/skills/openshift/rosa/rosa-aws-context)<a href="https://agentmods.dev/skills/openshift/rosa/rosa-aws-context"><img src="https://agentmods.dev/badge/skills/openshift/rosa/rosa-aws-context.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.00023 | $0.00347 |
| Opus 5 | $0.00012 | $0.00173 |
| Sonnet 5 | $0.00005 | $0.00069 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
ROSA AWS 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 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.
What it actually says
ROSA AWS Context
Use this skill when:
- Touching
pkg/aws/or AWS-related command flows - Editing AWS setup, prerequisites, or troubleshooting docs
- Changing wording around HCP, classic, STS, IAM, OIDC, VPC, subnet, quota, or region behavior
Workflow
- Read
AGENTS.mdandguidelines/aws-guidelines.md, then use the linked external ROSA and AWS references first. - Determine whether the change is HCP-only, classic-only, or shared.
- Cross-check architecture claims against the ROSA architecture docs before changing code comments, help text, or docs.
- Confirm prerequisite claims against the ROSA setup docs, especially quotas, support plans, SCP constraints, and STS token version notes.
- Validate AWS CLI install, profile, and config guidance against official AWS CLI documentation before editing examples.
- Prefer existing AWS helper functions and client wrappers over ad-hoc SDK usage.
- Do not silently bump AWS SDK or related dependency versions; if a bump is required, call it out explicitly, explain why, and validate downstream impact.
- Do not hardcode credentials or add logging that exposes secret material.
- If code behavior and official docs appear to disagree, surface the mismatch explicitly instead of guessing.
Verification
- Re-read the exact doc section that supports the changed behavior or wording.
- Check user-facing examples for current commands and options.
- Run the relevant local checks from
CONTRIBUTING.mdandMakefile.
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 · 31 lines · 23 tokens per session scan A 9b0550a46940
ROSA AWS Context is a skill published in the GitHub repository openshift/rosa (103 stars, last pushed yesterday), licensed Apache-2.0. It adds 23 tokens to every session and 347 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…