go-backend-scalability-cursorrules-prompt-file

go-backend-scalability-cursorrules-prompt-file is a cursor rule for Cursor from ItamarZand88/awesome-agent-conventions. It costs 1,246 tokens per session, scanned A, a copy of go-backend-scalability-cursorrules-prompt-file, MIT.

A set of Cursor rules for developing scalable Go backends. Cursor is a coding editor with built-in AI assistance; these rules guide its responses across topics such as APIs, databases, performance, testing, and deployment.

In plain words
What is it for?
Use it when asking for help with Go services, REST, GraphQL, or gRPC APIs, data stores, caching, scalability, security, Docker, Kubernetes, messaging, monitoring, and tests.
Why use it?
It gives the coding assistant project-wide direction for backend design and review instead of relying only on the wording of each individual request.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc). Also seen: positional $N argument; mentions Cursor.

Good fit Use it when asking for help with Go services, REST, GraphQL, or gRPC APIs, data stores, caching, scalability, security, Docker, Kubernetes, messaging, monitoring, and tests.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/itamarzand88/awesome-agent-conventions/go-backend-scalability-cursorrules-prompt-file
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ItamarZand88/awesome-agent-conventions

Made for: Cursor.

Wrote 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.

agentmods badge for go-backend-scalability-cursorrules-prompt-file

README.md
[![agentmods](https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/go-backend-scalability-cursorrules-prompt-file/github.svg)](https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/go-backend-scalability-cursorrules-prompt-file)
Your own site
<a href="https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/go-backend-scalability-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/go-backend-scalability-cursorrules-prompt-file/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.

agentmods 80×15 button for go-backend-scalability-cursorrules-prompt-file

Your own site · 80×15
<a href="https://agentmods.dev/rules/itamarzand88/awesome-agent-conventions/go-backend-scalability-cursorrules-prompt-file"><img src="https://agentmods.dev/badge/rules/itamarzand88/awesome-agent-conventions/go-backend-scalability-cursorrules-prompt-file.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,246 This file is loaded in full into every session.
When invoked 1,246 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 98% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01246 $0.01246
Opus 5 $0.00623 $0.00623
Sonnet 5 $0.00249 $0.00249
Haiku 4.5 $0.00125 $0.00125

Measured 11d ago against content hash d4692d3b0de2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

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 11d 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.

Origin

This is a copy

98% identical to go-backend-scalability-cursorrules-prompt-file — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

conventions/agent-rules/examples/awesome-cursorrules-go-backend-scalability/go-backend-scalability-cursorrules-prompt-file.mdc · 138 lines

How it starts

The opening of the file, as written. The whole thing — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.


description: "Cursor rules for Go development with backend scalability." globs: */ alwaysApply: false

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:

  1. Database Management (SQL, NoSQL, NewSQL)
  2. API Development (REST, GraphQL, gRPC)
  3. Server-Side Programming (Go, Rust, Java, Python, Node.js)
  4. Performance Optimization
  5. Scalability and Load Balancing
  6. Security Best Practices
  7. Caching Strategies
  8. Data Modeling
  9. Microservices Architecture
  10. Testing and Debugging
  11. Logging and Monitoring
  12. Containerization and Orchestration
  13. CI/CD Pipelines
  14. Docker and Kubernetes
  15. gRPC and Protocol Buffers
  16. Git Version Control
  17. Data Infrastructure (Kafka, RabbitMQ, Redis)
  18. Cloud Platforms (AWS, GCP, Azure)

When responding to queries:

  1. 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
  2. Provide clear, concise explanations of backend concepts and technologies

  3. Offer practical advice and best practices for real-world scenarios

  4. Share code snippets or configuration examples when appropriate, using proper formatting and syntax highlighting

  5. Explain trade-offs between different approaches when multiple solutions exist

  6. Consider scalability, performance, and security implications in your recommendations

  7. Reference official documentation or reputable sources when needed, but note that you don't have access to real-time information

  8. 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:

  1. The basics of gRPC and Protocol Buffers
  2. Go programming for gRPC server implementation
  3. Database interaction using Go's database/sql package or an ORM
  4. Best practices for structuring a gRPC service
  5. Error handling and data validation

I'll provide a step-by-step guide with code examples to illustrate the implementation.

  1. 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) {}
    }
    
  2. Generate Go code from the Proto file:

    protoc --go_out=. --go-grpc_out=. service.proto
    
  3. 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)
     }
    }
    

Read the full file on GitHub · 138 lines

Changes

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.

  1. 11d ago First seen · 138 lines · 1,246 tokens per session scan A d4692d3b0de2

Subscribe to this mod's changes

go-backend-scalability-cursorrules-prompt-file is a cursor rule published in the GitHub repository ItamarZand88/awesome-agent-conventions (31 stars, last pushed 1mo ago), licensed MIT. It adds 1,246 tokens to every session, about $0.0062 per session on Opus 5. A static security scan graded it A with 0 findings. It is 98% identical to go-backend-scalability-cursorrules-prompt-file, differing in 1 line, and is treated as a copy.