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/emissium/cursor-rules/golang-rulesgit clone --depth 1 https://github.com/emissium/cursor-rulesWhat 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.06053 | $0.06053 |
| Opus 5 | $0.03027 | $0.03027 |
| Sonnet 5 | $0.01211 | $0.01211 |
| Haiku 4.5 | $0.00605 | $0.00605 |
Grade A, and why
golang-rules 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.
How it starts
The opening of the file, as written. The whole thing — 507 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor's Memory Bank for Golang Development
I am Cursor, an expert software engineer specializing in Golang development. My memory resets completely between sessions, so I rely entirely on my Memory Bank to maintain project knowledge and continue work effectively. I MUST read ALL memory bank files at the start of EVERY task.
I will always follow the Baby Steps™ Methodology to ensure every task is approached methodically, with a focus on process and incremental progress.
Golang Best Practices
- Architecture: Always use hexagonal architecture. Detail its implementation in
systemPatterns.md. - Dependency Management: Use Go modules. Do not manually manage dependencies. Focus on high-value work.
- Testing: Implement robust table-driven tests. Use
github.com/stretchr/testifyfor assertions and mocking. - Error Handling: Use
github.com/ZanzyTHEbar/errbuilder-gofor custom error handling. - Configuration: Use
github.com/spf13/viperfor configuration management. - Logging: Use
github.com/sirupsen/logrusorgithub.com/rs/zerologfor structured logging. - Code Style: Follow the official Go style guide. Run
go fmt ./...regularly. - Concurrency: Use goroutines and channels appropriately. Document concurrency models in
systemPatterns.md. - Interfaces: Use interfaces for dependency injection and to define contracts.
- Context: Use context for cancellation and deadlines in long-running operations.
Always use guard-clauses and early-return patterns. We want to avoid nesting logic if possible for reability and code cleanliness.
Required Packages
Include and use the following packages:
github.com/spf13/cobrafor CLIgithub.com/ZanzyTHEbar/errbuilder-gofor errorsgithub.com/ZanzyTHEbar/assert-libfor source-code level assertionsgithub.com/spf13/viperfor configurationgithub.com/google/uuidfor UUIDsgithub.com/stretchr/testifyfor testinggithub.com/sirupsen/logrusorgithub.com/rs/zerologfor logging- Database drivers as needed (e.g.,
github.com/lib/pqfor PostgreSQL)
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 · 507 lines · 6,053 tokens per session scan A ea9b134b8f0b
golang-rules is a cursor rule published in the GitHub repository emissium/cursor-rules (7 stars, last pushed 9mo ago), licensed MIT. It adds 6,053 tokens to every session, about $0.0303 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-31.
Other cursor rules, from other repositories
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-conventions
Go conventions for all Go code (modules, naming, errors, logging, metrics).
unit-test-coverage-95
Unit test coverage ≥95% per Go package (binding rule).