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/15-100-go-mistakesgit 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/rules/openshift/rosa/15-100-go-mistakes)<a href="https://agentmods.dev/rules/openshift/rosa/15-100-go-mistakes"><img src="https://agentmods.dev/badge/rules/openshift/rosa/15-100-go-mistakes.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.00000 | $0.00313 |
| Opus 5 | $0.00000 | $0.00156 |
| Sonnet 5 | $0.00000 | $0.00063 |
| Haiku 4.5 | $0.00000 | $0.00031 |
Grade A, and why
15-100-go-mistakes 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 5d 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
Curated ROSA Adaptation Of 100 Go Mistakes
This is a supplemental checklist. AGENTS.md and 10-go-cobra-cli.mdc remain the primary ROSA guidance.
It is intentionally shorter than broader Terraform-oriented variants: keep only the footguns that reinforce ROSA CLI patterns without duplicating the repo-specific command, AWS, and testing rules above.
- Avoid variable shadowing, especially
err,ctx, and AWS or OCM clients. - Do not define interfaces too early. Prefer consumer-side interfaces and return concrete types unless the codebase already establishes an interface boundary.
- Wrap returned errors with context using
%w; do not drop the original error. - Do not store
context.Contextin structs. - Be explicit about nil versus empty slices only when behavior truly depends on it.
- Avoid magic numbers; extract named constants when the value matters to behavior or readability.
- Do not rely on map iteration order or goroutine scheduling in tests or production logic.
- Avoid
init()except where registration patterns truly require it. - Keep goroutines bounded and cancelable. Do not leak them during polling, retries, or test helpers.
- Prefer small focused functions and early returns over deeply nested branches.
- Use exported symbol doc comments when new public types or functions are introduced.
- Avoid reflection or
anywhen concrete types or small interfaces are clearer.
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.
- 5d ago First seen · 24 lines · 0 tokens per session scan A e64128dc99ee
15-100-go-mistakes is a cursor rule published in the GitHub repository openshift/rosa (103 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 313 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
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-conventions
Go conventions for all Go code (modules, naming, errors, logging, metrics).
go-grpc-service-rule
在 Go 中实现 gRPC 服务的具体指南。.
go
Go conventions for all Zapstore Go projects (zsp, server, zindex, zapstore-cli).