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/mitas/cursor-rulesWrote 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/mitas/cursor-rules/golang)<a href="https://agentmods.dev/rules/mitas/cursor-rules/golang"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/golang/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/mitas/cursor-rules/golang"><img src="https://agentmods.dev/badge/rules/mitas/cursor-rules/golang.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.00000 | $0.02532 |
| Opus 5.5 | $0.00000 | $0.01013 |
| Sonnet 5.5 | $0.00000 | $0.00506 |
| Haiku 4.5 | $0.00000 | $0.00253 |
Grade A, and why
golang 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.
How it starts
The opening of the file, as written. The whole thing — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go (Golang) Coding Standards
Project Structure
Note: For comprehensive project structure guidelines, refer to golang-project-structure.mdc
- Organize code into logical packages
- Package names should be lowercase, short, and not plural
- Follow the standard Go project layout (cmd/, pkg/, internal/)
- Use
/internalfor code not meant to be imported by other projects - Separate models, services, and controllers
- Group related functionality in the same package
- Implement repository pattern for data access
- Organize tests in the same package as production code with
_test.gosuffix
Interfaces and Types
Interface Design
- No pointers to interfaces: pass interfaces as values
- Verify interface compliance at compile time:
var _ Interface = (*Implementation)(nil) - Keep interfaces small and focused (ideally 1-3 methods)
- Use interfaces at package boundaries for better testing
- Design interfaces for consumers, not implementations
- Don't export interfaces for concrete types with a single implementation
Method Receivers
- Use value receivers for methods that don't modify the receiver
- Use pointer receivers for methods that modify the receiver
- Be consistent with receiver types for the same struct
- Methods with value receivers can be called on pointers as well as values
- Methods with pointer receivers can only be called on pointers or addressable values
- If any method requires a pointer receiver, use pointer receivers for all methods
Type Assertions
- Always use the "comma ok" idiom:
val, ok := x.(T) - Don't use type assertions without checking the result
- Use type switches for multiple potential types
- Consider using the
errors.Asfunction for error type checking
Error Handling
Error Creation
- Return errors instead of using panic
- Create specialized error types for specific error cases
- Implement Error() string method for custom error types
- Use
errors.Newfor simple errors - Add context when wrapping errors:
fmt.Errorf("doing X: %w", err) - Use
%wverb for error wrapping to preserve the original error
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 · 298 lines · 2,532 tokens per session scan A 2efb57364b30
golang is a cursor rule published in the GitHub repository mitas/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,532 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-31.
Other cursor rules, from other repositories
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
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.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
go-grpc-service-rule
A set of Chinese-language rules for implementing gRPC services in Go. gRPC is a way for software services to communicate using defined messages and procedures.