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.
git clone --depth 1 https://github.com/ofershap/go-best-practicesWrote 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/ofershap/go-best-practices/best-practices)<a href="https://agentmods.dev/rules/ofershap/go-best-practices/best-practices"><img src="https://agentmods.dev/badge/rules/ofershap/go-best-practices/best-practices/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/ofershap/go-best-practices/best-practices"><img src="https://agentmods.dev/badge/rules/ofershap/go-best-practices/best-practices.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00259 | $0.00259 |
| Opus 5.5 | $0.00104 | $0.00104 |
| Sonnet 5.5 | $0.00052 | $0.00052 |
| Haiku 4.5 | $0.00026 | $0.00026 |
Grade A, and why
best-practices 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 1mo 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
When writing or modifying Go code:
-
Wrap all errors with context — Use
fmt.Errorf("context: %w", err)instead ofreturn err. Never propagate bare errors. -
Use slog for logging — Use
log/slog(slog.Info, slog.Error, slog.Debug) instead oflogpackage. No log.Printf. -
Context as first parameter — Pass
context.Contextas the first argument to functions. Never store context in struct fields. -
Error checking — Use
errors.Is(err, target)anderrors.As(err, &target)for error checks. Never use==or type assertion on errors. -
Go 1.22+ patterns — Prefer
for i := range noverfor i := 0; i < n; i++. Do not add unnecessary loop variable shadow copies (Go 1.22 fixed capture). -
Goroutine lifecycle — Every goroutine must have an exit path. Use context cancellation, done channels, or errgroup. Never spawn unbounded goroutines that cannot stop.
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.
- 1mo ago First seen · 19 lines · 259 tokens per session scan A cea0dc8ee7e7
best-practices is a cursor rule published in the GitHub repository ofershap/go-best-practices (2 stars, last pushed 8mo ago), licensed MIT. It adds 259 tokens to every session, about $0.0010 per session on Opus 5.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-31.
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.
go-handler
Patterns for Go handler layer files — HTTP request handling, validation, routing.
go-service
Patterns for Go service layer files — business logic, DB access, auth checks.
cursor-rule-template
A Cursor rule template for gospec, a set of software-development rules for Go backends. It routes different tasks to the relevant architecture, API, data, security, testing, and migration guidance.
go-idiomatic-code
This rule ensures that all Go code follows idiomatic Go practices, adhering to the official Go style guide and common best practices in the Go community.
go-project-structure
This rule ensures that Go projects follow a consistent and idiomatic structure, making the codebase easier to navigate, maintain, and scale.