awesome-cursor-rules-mdc is a generator that creates Cursor MDC rule files from structured library information, using semantic search and language models to gather and organize guidance. Developers use it to produce reusable rules for libraries in Cursor, and the catalogue includes 200 of those rules.
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/sanjeed5/awesome-cursor-rules-mdcWrote 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/sanjeed5/awesome-cursor-rules-mdc/fiber)<a href="https://agentmods.dev/rules/sanjeed5/awesome-cursor-rules-mdc/fiber"><img src="https://agentmods.dev/badge/rules/sanjeed5/awesome-cursor-rules-mdc/fiber.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.02979 | $0.02979 |
| Opus 5 | $0.01489 | $0.01489 |
| Sonnet 5 | $0.00596 | $0.00596 |
| Haiku 4.5 | $0.00298 | $0.00298 |
Grade A, and why
fiber 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 4d 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 — 416 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fiber Best Practices
Fiber is a high-performance, Express-inspired web framework for Go, built on fasthttp. These rules ensure we leverage Fiber's speed and maintainability while avoiding common pitfalls.
1. Core Principle: fiber.Ctx Immutability
NEVER retain references to fiber.Ctx or any data extracted from it (like c.Params, c.Query, c.Body) after the handler returns. fiber.Ctx values are reused across requests, making their contents ephemeral. Always copy data if you need to store it.
❌ BAD: Retaining ephemeral data
package handlers
import (
"github.com/gofiber/fiber/v2"
"log"
)
// This struct will hold a reference to the ephemeral string
type UserRequest struct {
UserID string
}
func GetUserBad(c *fiber.Ctx) error {
// DANGER: c.Params("id") returns an ephemeral string.
// Storing it directly will lead to data corruption in future requests.
req := &UserRequest{
UserID: c.Params("id"),
}
// Simulating async processing or storage
go func() {
// By the time this goroutine runs, c.Params("id") might have changed
log.Printf("Processing user ID: %s", req.UserID) // Will likely be wrong
}()
return c.SendString("Request received (bad example)")
}
✅ GOOD: Copying ephemeral data
package handlers
import (
"github.com/gofiber/fiber/v2"
"github.com/gofiber/fiber/v2/utils" // Use Fiber's utility for efficient copying
"log"
)
// This struct holds a safe copy of the string
type UserRequest struct {
UserID string
}
func GetUserGood(c *fiber.Ctx) error {
// ALWAYS copy data from c.Params, c.Query, c.Body, etc.
userID := utils.CopyString(c.Params("id"))
req := &UserRequest{
UserID: userID,
}
// Simulating async processing or storage
go func() {
// This is safe; userID is a distinct copy
log.Printf("Processing user ID: %s", req.UserID) // Will always be correct
}()
return c.SendString("Request received (good example)")
}
2. Code Organization and Structure
Organize your application into logical layers: main, config, router, middleware, handlers, services, repository, models, utils.
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.
- 4d ago First seen · 416 lines · 2,979 tokens per session scan A 0d272da42be7
fiber is a cursor rule published in the GitHub repository sanjeed5/awesome-cursor-rules-mdc (3,571 stars, last pushed 3mo ago), licensed CC0-1.0. It adds 2,979 tokens to every session, about $0.0149 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-09-03.
Other cursor rules, from other repositories
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
go-servemux-rest-api-cursorrules-prompt-file
Cursor rules for Go development with ServeMux REST API integration.
tech-rules
You are an expert AI programming assistant specializing in building APIs with Go, using gin web framework in Go 1.22 or newer. Always use the latest stable version of Go (1.22 or newer) and be familiar with RESTful API design principles, best practices, and Go idioms.
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.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
go-grpc-service-rule
A set of Chinese-language rules for implementing gRPC services in Go. gRPC is a way for software services to communicate using defined messages and procedures.