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/chand1012/cursorrules/gogit clone --depth 1 https://github.com/chand1012/cursorrulesWhat 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.00829 |
| Opus 5 | $0.00000 | $0.00415 |
| Sonnet 5 | $0.00000 | $0.00166 |
| Haiku 4.5 | $0.00000 | $0.00083 |
Grade A, and why
go 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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Best Practices
Package and Import Statements
- Use meaningful package names that reflect their purpose (e.g.,
auth,config). - Group imports in this order: standard library, third-party, then local packages, separated by blank lines.
- Avoid import cycles to maintain clean dependency graphs.
Type System
- Use
structtypes to define complex data structures. - Define
interfacetypes to specify behavior and enable polymorphism. - Use type aliases sparingly for clarity (e.g.,
type ID string). - Leverage Go’s built-in types (e.g.,
map,slice) and composite types effectively. - Avoid unnecessary type conversions to maintain type safety.
- Use struct embedding for composition instead of inheritance.
Naming Conventions
- Use
camelCasefor variable and function names (e.g.,getUser). - Use
PascalCasefor type names and exported identifiers (e.g.,UserService). - Use
ALL_CAPSfor constants (e.g.,MAX_RETRIES). - Be descriptive yet concise in naming (e.g.,
userCountovercnt).
Code Organization
- Follow the standard Go project layout (e.g.,
cmd/,pkg/,internal/). - Keep related code within the same package for cohesion.
- Use subdirectories for larger packages to organize functionality (e.g.,
api/handlers).
Functions and Methods
- Keep functions short and focused on a single responsibility.
- Use named return values for clarity in complex functions (e.g.,
func getData() (data string, err error)). - Avoid side effects in functions to improve predictability.
Best Practices
- Follow the Go proverb: "A little copying is better than a little dependency."
- Use interfaces to define behavior and decouple components.
- Prefer composition over inheritance using embedding.
- Avoid unnecessary abstractions; prioritize simplicity.
- Use the
initfunction sparingly for package initialization. - Avoid global variables; if unavoidable, ensure they are thread-safe (e.g., with
sync.Mutex). - Be mindful of memory allocations; use profiling tools (e.g.,
pprof) to optimize performance. - Use
gofmtfor consistent formatting andgo vetfor static analysis.
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 · 73 lines · 829 tokens per session scan A 0dde40e169ac
go is a cursor rule published in the GitHub repository chand1012/cursorrules (13 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 829 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-30.
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.
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.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
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.