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-eng/ai-helpers/idiomatic-gogit clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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-eng/ai-helpers/idiomatic-go)<a href="https://agentmods.dev/rules/openshift-eng/ai-helpers/idiomatic-go"><img src="https://agentmods.dev/badge/rules/openshift-eng/ai-helpers/idiomatic-go.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.00281 | $0.00281 |
| Opus 5 | $0.00140 | $0.00140 |
| Sonnet 5 | $0.00056 | $0.00056 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
idiomatic-go 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 3d 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
Idiomatic Go Code
When writing Go code, always follow the guidelines from Effective Go.
Required Actions
- Before writing any Go code, reference https://go.dev/doc/effective_go and apply its principles
- Run
gofmt -w .on all Go files before committing - Run
go vetto catch common mistakes - Follow naming conventions: MixedCaps for exported, mixedCaps for unexported
- Handle all errors explicitly - never ignore error return values
- Use idiomatic patterns:
- Prefer small interfaces
- Share memory by communicating (use channels)
- Return errors, don't panic
- Use defer for cleanup
- Accept interfaces, return concrete types
Common Anti-Patterns to Avoid
- Using
panicfor normal error handling - Ignoring errors with
_ - Communicating by sharing memory instead of using channels
- Large, unfocused interfaces
- Package names with underscores or mixedCaps
- Storing
context.Contextin structs
Reference
See Effective Go for comprehensive guidelines and Go Code Review Comments for additional best practices.
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.
- 3d ago First seen · 31 lines · 281 tokens per session scan A 1497e2c17bdf
idiomatic-go is a cursor rule published in the GitHub repository openshift-eng/ai-helpers (114 stars, last pushed today), licensed Apache-2.0. It adds 281 tokens to every session, about $0.0014 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 cursor rules, from other repositories
1c-form-reserved-names
Зарезервированные имена свойств в модулях форм 1С.
django-middleware
关于使用 Django 中间件处理认证、日志和缓存等横切关注点的指南。.
typescript-coding-rule
It allows a subset of JSDoc tags. Most tags must occupy their own line, with the tag at the beginning of the line.
typescript
// Bad const data: any = JSON.parse(content).
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
java-17-development-standards
Java-specific development standards following Effective Java, Google Java Style Guide, and modern Java 17 LTS best practices.