agentmods.dev

rosa AGENTS.md

Repository instructions for the ROSA command-line tool, which manages Red Hat OpenShift Service on AWS. They identify the repository boundaries, important reference files, and precautions for changes to customer-facing commands.

In plain words
What is it for?
Use them when changing the Go CLI, its commands, tests, build files, generated files, or contribution workflow.
Why use it?
They show a coding agent where to find build, test, contribution, and generation rules before editing the code. This lowers the risk of breaking release checks or command behavior.

Instructions file for CodexOpenCode

103 2d ago A scan 2,755 tokens original Apache-2.0
View the source file openshift/rosa
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 instructions/openshift/rosa/agents-md
Clone the repo
git clone --depth 1 https://github.com/openshift/rosa

Made for: Codex, OpenCode.

Per session 2,755 This file is loaded in full into every session.
When invoked 2,755 The same file — it is already loaded in full.
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.02755 $0.02755
Opus 5 $0.01378 $0.01378
Sonnet 5 $0.00551 $0.00551
Haiku 4.5 $0.00276 $0.00276

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

Security

Grade A, and why

rosa AGENTS.md 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.

AGENTS.md · 211 lines

How it starts

The opening of the file, as written. The whole thing — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AGENTS.md

This is the central repo-local guidance for agents working inside openshift/rosa.

Use this file as the starting point for repository context. When this file points to an exact command source, template, hook script, or generated-file workflow, treat that referenced file as the authoritative procedure.

Repository Scope

  • openshift/rosa is the ROSA CLI: a public-facing Go CLI for managing Red Hat OpenShift Service on AWS (ROSA).
  • This repository ships frequently and supports real customer workflows. Be conservative. Small mistakes can break release builds, presubmits, E2E flows, or user-facing command behavior.
  • The human submitter owns every change. Agents are helpers, not decision makers.
  • Do not perform release work or release automation from an agent session.
  • Do not duplicate code from the Go standard library or vendored dependencies when an existing implementation already covers the need.

Key Reference Files

  • CONTRIBUTING.md
    • Contributor workflow, hook installation, required local checks, commit format, and CI expectations.
  • Makefile
    • Supported local build, test, format, and generation commands.
  • .github/pull_request_template.md
    • Required PR structure, validation notes, and reviewer-facing checklist.
  • .githooks/pre-commit, .githooks/pre-push, .githooks/commit-msg
    • Hook entrypoints used by local git workflow.
  • hack/pre-commit-hook.sh, hack/pre-push-hook.sh, hack/commit-msg-hook.sh, hack/commit-msg-verify.sh
    • Exact local validation and commit-message behavior.
  • cmd/rosa/structure_test/command_structure.yml
    • CLI command tree contract.
  • cmd/rosa/structure_test/command_args/**/command_args.yml
    • Supported flag contract for each command.

Docs Index

  • guidelines/ARCHITECTURE.md
    • High-level CLI layering, external-system boundaries, and change-risk hotspots.
  • guidelines/aws-guidelines.md
    • AWS and ROSA architecture checks, prerequisite handling, secret safety, and dependency-bump guardrails.
  • guidelines/command-guidelines.md
    • CLI command authoring expectations, structure-test alignment, and reporter/output patterns.
  • guidelines/testing-guidelines.md
    • Test style, generated-file boundaries, validation paths, and PR-readiness checklist use.
  • guidelines/workflow-conventions.md
    • Request and Result type naming, construction, optional-value handling, and the lifecycle for reusable workflow functions in pkg/.

Read the full file on GitHub · 211 lines

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 · 211 lines · 2,755 tokens per session scan A 4d20eaac74d9

Subscribe to this mod's changes

rosa AGENTS.md is an instructions file published in the GitHub repository openshift/rosa (103 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,755 tokens to every session, about $0.0138 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.

DevOps and cloudTestingWriting and docs
Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens