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/openshift/rosa/10-go-cobra-cligit 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.00000 | $0.00260 |
| Opus 5 | $0.00000 | $0.00130 |
| Sonnet 5 | $0.00000 | $0.00052 |
| Haiku 4.5 | $0.00000 | $0.00026 |
Grade A, and why
10-go-cobra-cli 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 Go And Cobra
- Prefer thin Cobra command files. 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. - Follow machinepool commands and nearby code for patterns before creating new command shapes.
- Keep error handling consistent with reporter usage, exit behavior, and surrounding package messages.
- Update command structure contracts when commands or flags change:
cmd/rosa/structure_test/command_structure.yml- matching
cmd/rosa/structure_test/command_args/**/command_args.yml
- Do not change imports, run
go mod tidy, or rungo mod vendorunless the task explicitly requires it. - Use descriptive names and repo casing conventions such as
...Hcp. - Keep user-facing output consistent with
pkg/output,pkg/reporter, andpkg/interactive.
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 · 20 lines · 0 tokens per session scan A b9e423c08a01
10-go-cobra-cli 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 260 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.
Other cursor rules, from other repositories
atmos-rules
This is a Golang CLI project using Cobra for command structure and Viper for configuration management. The project maintains high code quality standards through golangci-lint and aims for maximum test coverage. The repository also includes the website source code for https://atmos.tools.
cursor-go-skills
Load the Go skills orchestrator before any Go task.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
code-style
Formatting, lint, comments language.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
go-grpc-service-rule
在 Go 中实现 gRPC 服务的具体指南。.