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-command-authoringnpx skills add openshift/rosa --skill rosa-command-authoringgit clone --depth 1 https://github.com/openshift/rosaWhat 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.00029 | $0.00352 |
| Opus 5 | $0.00015 | $0.00176 |
| Sonnet 5 | $0.00006 | $0.00070 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
ROSA Command Authoring 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.
What it actually says
ROSA Command Authoring
Use this skill when:
- Adding a new
rosacommand or subcommand - Changing flags or command help
- Moving logic between
cmd/andpkg/ - Refactoring command execution flow
Workflow
- Read
AGENTS.mdandguidelines/command-guidelines.md, then inspect the nearest similar command implementation. - Keep Cobra command files thin and move non-Cobra logic into
pkg/. - Follow the entrypoint and exit pattern already established in the nearest similar command area.
- Many ROSA commands use
Run: run; do not switch a command area betweenRunandRunE, or add/remove directos.Exit()calls, unless the surrounding pattern already does so and the change keeps behavior consistent. - Reuse
output,reporter, andinteractivepatterns already used by the surrounding command area. - If the command tree changes, update
cmd/rosa/structure_test/command_structure.yml. - If supported flags change, update the matching
cmd/rosa/structure_test/command_args/**/command_args.yml. - When command help or docs change, check whether
make generate-docsis part of the required verification.
Verification
make fmt- relevant package tests or
make test make rosamake generate-docswhen command docs or help output changed
Follow CONTRIBUTING.md for the exact contributor workflow and hook expectations.
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.
- 2d ago First seen · 34 lines · 29 tokens per session scan A 07fe676751e3
ROSA Command Authoring is a skill published in the GitHub repository openshift/rosa (103 stars, last pushed 2d ago), licensed Apache-2.0. It adds 29 tokens to every session and 352 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
golang
Go coding standards and conventions for this project. Apply when writing, reviewing, or refactoring any Go source file.
go-naming
Go naming conventions and best practices. Use this skill when working with Go code and need to name packages, files, directories, structs, interfaces, functions, variables, or constants. Provides comprehensive naming guidelines following Go community standards.
developer-code-organization
Code organization patterns, file structure guidelines, WASM build variants, and string processing conventions for gh-aw Go code.
gen-test
Generate idiomatic tests for Go packages and handlers in the Meshery project.
higress-wasm-go-plugin
Develop Higress WASM plugins using Go 1.24+. Use when creating, modifying, or debugging Higress gateway plugins for HTTP request/response processing, external service calls, Redis integration, or custom gateway logic.
gentleman-bubbletea
Bubbletea TUI patterns for Gentleman.Dots installer. Trigger: When editing Go files in installer/internal/tui/, working on TUI screens, or adding new UI features.