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/FreePeak/cortexWrote 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/freepeak/cortex/go-architecture)<a href="https://agentmods.dev/rules/freepeak/cortex/go-architecture"><img src="https://agentmods.dev/badge/rules/freepeak/cortex/go-architecture/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/freepeak/cortex/go-architecture"><img src="https://agentmods.dev/badge/rules/freepeak/cortex/go-architecture.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.01789 | $0.01789 |
| Opus 5.5 | $0.00716 | $0.00716 |
| Sonnet 5.5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade A, and why
go-architecture 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IDE Cursor Rules for Golang Development
Architecture & Structure
-
Clean Architecture
- Maintain clear separation between layers: domain, repository, usecase, handler
- Follow dependency rule: inner layers must not depend on outer layers
- Domain entities should not have dependencies on frameworks or external libraries
- Use dependency injection for infrastructure dependencies
-
Project Structure
root/ ├── cmd │ ├── app │ └── tools ├── config ├── documents ├── internal │ ├── domain │ │ ├── authentication │ │ ├── shared │ │ │ ├── errors │ │ │ └── valueobjects │ │ └── user │ ├── infrastructure │ │ ├── background │ │ ├── db │ │ │ ├── migrations │ │ │ └── repository │ │ ├── file_storage │ │ ├── filestorage │ │ ├── logging │ │ ├── server │ │ └── temporal │ ├── interfaces │ │ ├── persistence │ │ └── rest │ ├── middleware │ ├── shared │ └── usecases ├── pkg │ └── utils
3. **Domain-Driven Design**
- Model domain entities around business concepts
- Use value objects for immutable concepts
- Implement aggregate roots to maintain consistency boundaries
- Define repository interfaces in the domain layer
- Keep business logic in domain entities or domain services
## Code Quality Principles
4. **SOLID Principles**
- **Single Responsibility**: Each struct/function should have only one reason to change
- **Open/Closed**: Extend behavior through interfaces rather than modification
- **Liskov Substitution**: Interface implementations must be substitutable
- **Interface Segregation**: Prefer small, focused interfaces (1-3 methods)
- **Dependency Inversion**: Depend on abstractions, not concrete implementations
5. **DRY (Don't Repeat Yourself)**
- Extract common functionality into shared packages
- Use middleware for cross-cutting concerns
- Create utility functions for repeated operations
- Implement generic repository patterns where appropriate
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 · 249 lines · 1,789 tokens per session scan A d0376f9fb01f
go-architecture is a cursor rule published in the GitHub repository FreePeak/cortex (27 stars, last pushed 1y ago), licensed Apache-2.0. It adds 1,789 tokens to every session, about $0.0072 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-30.
Other cursor rules, from other repositories
global
You are an expert in Golang, TypeScript, and JavaScript development, focusing on scalable, maintainable, and performant code. Follow these principles for all suggestions, code generation, and responses.
zz_generated.go-llm-rules
Cursor rule "zz_generated.go-llm-rules" from giantswarm/mcp-prometheus, covering go code guidelines and formatting.
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.