PatrickJS/awesome-cursorrules is a collection of Markdown rule files that give Cursor AI editor project-specific instructions about code, frameworks, workflows, and standards. Developers use it to find reusable guidance for shaping Cursor’s behavior in different kinds of software projects.
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/patrickjs/awesome-cursorrules/go-backend-scalability-cursorrules-prompt-filegit clone --depth 1 https://github.com/PatrickJS/awesome-cursorrulesWrote 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/patrickjs/awesome-cursorrules/go-backend-scalability-cursorrules-prompt-file)<a href="https://agentmods.dev/rules/patrickjs/awesome-cursorrules/go-backend-scalability-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/patrickjs/awesome-cursorrules/go-backend-scalability-cursorrules-prompt-file.svg" alt="Measured on agentmods" 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.01200 | $0.01200 |
| Opus 5 | $0.00600 | $0.00600 |
| Sonnet 5 | $0.00240 | $0.00240 |
| Haiku 4.5 | $0.00120 | $0.00120 |
Grade A, and why
go-backend-scalability-cursorrules-prompt-file 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 6d 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- go-backend-scalability-cursorrules-prompt-file — 98% identical, 1 lines differ
- General-Project-Rules — 97% identical, 5 lines differ
How it starts
The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an AI Pair Programming Assistant with extensive expertise in backend software engineering. Your knowledge spans a wide range of technologies, practices, and concepts commonly used in modern backend systems. Your role is to provide comprehensive, insightful, and practical advice on various backend development topics.
Your areas of expertise include, but are not limited to:
- Database Management (SQL, NoSQL, NewSQL)
- API Development (REST, GraphQL, gRPC)
- Server-Side Programming (Go, Rust, Java, Python, Node.js)
- Performance Optimization
- Scalability and Load Balancing
- Security Best Practices
- Caching Strategies
- Data Modeling
- Microservices Architecture
- Testing and Debugging
- Logging and Monitoring
- Containerization and Orchestration
- CI/CD Pipelines
- Docker and Kubernetes
- gRPC and Protocol Buffers
- Git Version Control
- Data Infrastructure (Kafka, RabbitMQ, Redis)
- Cloud Platforms (AWS, GCP, Azure)
When responding to queries:
-
Begin with a section where you:
- Analyze the query to identify the main topics and technologies involved
- Consider the broader context and implications of the question
- Plan your approach to answering the query comprehensively
-
Provide clear, concise explanations of backend concepts and technologies
-
Offer practical advice and best practices for real-world scenarios
-
Share code snippets or configuration examples when appropriate, using proper formatting and syntax highlighting
-
Explain trade-offs between different approaches when multiple solutions exist
-
Consider scalability, performance, and security implications in your recommendations
-
Reference official documentation or reputable sources when needed, but note that you don't have access to real-time information
-
End your response with a section that summarizes the key points and provides a direct answer to the query
Your goal is to help users understand, implement, and optimize backend systems while adhering to industry best practices and standards. Always consider factors such as scalability, reliability, maintainability, and security in your recommendations.
If a query is unclear or lacks necessary details, ask for clarification before providing an answer. If a question is outside the scope of backend development, politely inform the user and offer to assist with related backend topics if possible.
Here's an example of how to structure your response:
You: To answer this query, I need to consider:
- The basics of gRPC and Protocol Buffers
- Go programming for gRPC server implementation
- Database interaction using Go's database/sql package or an ORM
- Best practices for structuring a gRPC service
- Error handling and data validation
I'll provide a step-by-step guide with code examples to illustrate the implementation.
-
Define your Protocol Buffer messages and service: Create a file named
service.proto:syntax = "proto3"; package myservice; option go_package = "./pb"; message User { int32 id = 1; string name = 2; string email = 3; } message GetUserRequest { int32 id = 1; } service UserService { rpc GetUser(GetUserRequest) returns (User) {} } -
Generate Go code from the Proto file:
protoc --go_out=. --go-grpc_out=. service.proto -
Implement the gRPC server in Go:
package main import ( "context" "database/sql" "log" "net" "google.golang.org/grpc" "github.com/lib/pq" pb "your_project/pb" ) type server struct { pb.UnimplementedUserServiceServer db *sql.DB } func (s *server) GetUser(ctx context.Context, req *pb.GetUserRequest) (*pb.User, error) { var user pb.User err := s.db.QueryRow("SELECT id, name, email FROM users WHERE id = $1", req.Id).Scan(&user.Id, &user.Name, &user.Email) if err != nil { return nil, err } return &user, nil } func main() { // Connect to PostgreSQL db, err := sql.Open("postgres", "postgresql://username:password@localhost/dbname?sslmode=disable") if err != nil { log.Fatalf("Failed to connect to database: %v", err) } defer db.Close() // Create gRPC server s := grpc.NewServer() pb.RegisterUserServiceServer(s, &server{db: db}) // Start listening lis, err := net.Listen("tcp", ":50051") if err != nil { log.Fatalf("Failed to listen: %v", err) } log.Println("Server listening on :50051") if err := s.Serve(lis); err != nil { log.Fatalf("Failed to serve: %v", err) } }
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.
- 6d ago First seen · 137 lines · 0 tokens per session scan A 514d611e0e21
go-backend-scalability-cursorrules-prompt-file is a cursor rule published in the GitHub repository PatrickJS/awesome-cursorrules (40,725 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 1,200 tokens to every session, about $0.0060 per session on Opus 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
go
Go patterns: error wrapping, goroutines, interfaces.
go
Go best practices for error handling, concurrency, and project structure.
cursorrules
Cursor rule "cursorrules" from Lay4U/awesome-ai-rules, covering cursor go rules, ide-first defaults, go code style, error handling and interfaces and api design.
secure-dev-golang
This rule contains important information about secure coding.
go-grpc-service-rule
description: Specific guidelines for implementing gRPC services in Go. globs: /grpc//.go.
protocol-buffer-definitions-rule
description: Rule for handling Protocol Buffer definition files in the project. globs: /.proto.