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/mitas/cursor-rules/golang-project-structuregit clone --depth 1 https://github.com/mitas/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.00000 | $0.01997 |
| Opus 5 | $0.00000 | $0.00999 |
| Sonnet 5 | $0.00000 | $0.00399 |
| Haiku 4.5 | $0.00000 | $0.00200 |
Grade A, and why
golang-project-structure 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 yesterday.
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 — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Project Structure Best Practices
Core Principles
- Your project structure should reflect its complexity and size
- Follow the standard Go project layout for consistency and maintainability
- Package names should be lowercase, short, and not plural
- Group related functionality in the same package
- Keep package dependencies minimal and avoid circular dependencies
- Use internal directories for code not meant for external use
- Strictly separate application configuration from business logic
Recommended Project Structures
Flat Structure
For small projects and prototypes:
project/
├── main.go # Application entry point
├── handler.go # HTTP handlers
├── service.go # Business logic
├── repository.go # Database repository
├── config.go # Configuration settings
├── utils.go # Utility functions
├── go.mod # Go module file
└── go.sum # Go module dependency file
When to use:
- Small utility applications
- Prototypes and MVPs
- Simple command-line tools
- Learning projects
Standard Layout
For medium to large applications:
project/
├── cmd/ # Main applications
│ └── app/ # Application entry point
│ └── main.go # Main application logic
├── internal/ # Private application code
│ ├── handlers/ # HTTP request handlers
│ │ └── user_handler.go # User-specific handler
│ ├── services/ # Business logic layer
│ │ └── user_service.go # User-specific service
│ ├── repositories/ # Data access layer
│ │ └── user_repo.go # User-specific repository
│ └── models/ # Data models
│ └── user.go # User model
├── pkg/ # Public libraries for external use
│ └── common/ # Common utilities
├── configs/ # Configuration files
│ └── config.yaml # Application config
├── api/ # API definitions (OpenAPI/Swagger)
├── web/ # Web assets (templates, static files)
├── docs/ # Documentation
├── scripts/ # Build and deployment scripts
├── test/ # Additional test resources
├── go.mod # Go module definition
└── go.sum # Go module checksums
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.
- yesterday First seen · 251 lines · 1,997 tokens per session scan A 7325cd9bf172
golang-project-structure 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 1,997 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.