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/compozy/gographWrote 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/compozy/gograph/go-patterns)<a href="https://agentmods.dev/rules/compozy/gograph/go-patterns"><img src="https://agentmods.dev/badge/rules/compozy/gograph/go-patterns/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/compozy/gograph/go-patterns"><img src="https://agentmods.dev/badge/rules/compozy/gograph/go-patterns.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.01990 | $0.01990 |
| Opus 5.5 | $0.00796 | $0.00796 |
| Sonnet 5.5 | $0.00398 | $0.00398 |
| Haiku 4.5 | $0.00199 | $0.00199 |
Grade A, and why
go-patterns 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 — 366 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Core Go Patterns & Conventions
Concurrency Patterns
Factory Pattern (OCP Implementation)
type StorageFactory struct{} func (f *StorageFactory) CreateStorage(storageType string) (Storage, error) { switch storageType { case "redis": return NewRedisStorage(), nil case "memory": return NewMemoryStorage(), nil default: return nil, fmt.Errorf("unsupported storage type: %s", storageType) } }
// Usage in constructors func NewStorage(config *StorageConfig) (Storage, error) { factory := &StorageFactory{} return factory.CreateStorage(config.Type) }
</pattern>
## Configuration with Defaults
<requirement type="always">
**Always provide defaults:**
</requirement>
<pattern type="configuration_defaults">
```go
func NewService(config *Config) *Service {
if config == nil {
config = DefaultConfig() // Always provide defaults
}
return &Service{config: config}
}
func DefaultServiceConfig() *ServiceConfig { return &ServiceConfig{ Port: 8080, Timeout: 30 * time.Second, MaxRetries: 3, } }
func NewServiceFromConfig(cfg *ServiceConfig) *Service { if cfg == nil { cfg = DefaultServiceConfig() } return &Service{config: cfg} }
</pattern>
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 · 366 lines · 1,990 tokens per session scan A 1a3e88074e5f
go-patterns is a cursor rule published in the GitHub repository compozy/gograph (9 stars, last pushed 1y ago), licensed MIT. It adds 1,990 tokens to every session, about $0.0080 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
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
Go conventions for all Zapstore Go projects (zsp, server, zindex, zapstore-cli).