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/madebyaris/poinf-of-salesWrote 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/madebyaris/poinf-of-sales/backend-golang)<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/backend-golang"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/backend-golang/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.
<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/backend-golang"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/backend-golang.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.01014 |
| Opus 5 | $0.00000 | $0.00507 |
| Sonnet 5 | $0.00000 | $0.00203 |
| Haiku 4.5 | $0.00000 | $0.00101 |
Grade A, and why
backend-golang 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 13d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backend Development Guidelines (Golang)
Code Organization
Package Structure
Follow the backend/internal/ package layout:
models/- Data structures and DTOshandlers/- HTTP request handlersmiddleware/- HTTP middleware functionsdatabase/- Database connection and utilitiesapi/- Route definitions and setuputils/- Shared utility functions
Handler Pattern
All handlers follow the pattern in handlers/orders.go:
type OrderHandler struct {
db *sql.DB
}
func NewOrderHandler(db *sql.DB) *OrderHandler {
return &OrderHandler{db: db}
}
func (h *OrderHandler) GetOrders(c *gin.Context) {
// Implementation
}
Database Operations
Raw SQL Usage
- Use parameterized queries to prevent SQL injection
- Follow the patterns in handlers/orders.go for database operations
- Always handle
sql.ErrNoRowsexplicitly - Use transactions for multi-table operations
Example Query Pattern:
func (h *Handler) getRecord(id uuid.UUID) (*Model, error) {
var record Model
query := `SELECT id, field1, field2 FROM table WHERE id = $1`
err := h.db.QueryRow(query, id).Scan(&record.ID, &record.Field1, &record.Field2)
if err == sql.ErrNoRows {
return nil, fmt.Errorf("record not found")
}
if err != nil {
return nil, fmt.Errorf("database error: %w", err)
}
return &record, nil
}
Authentication & Security
JWT Middleware
Use the authentication middleware from middleware/auth.go:
- Protected routes must use
authMiddleware - Role-based access with
RequireRoles([]string{"admin", "manager"}) - Extract user info with
GetUserFromContext(c)
Error Handling
Follow the API response pattern from models/models.go:
c.JSON(http.StatusBadRequest, models.APIResponse{
Success: false,
Message: "User-friendly error message",
Error: stringPtr("error_code"),
})
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.
- 13d ago First seen · 146 lines · 1,014 tokens per session scan A de4d70f53d3a
backend-golang is a cursor rule published in the GitHub repository madebyaris/poinf-of-sales (142 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,014 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
write
Writing style guide with AI detection avoidance. For tweets, LinkedIn, blogs, READMEs, commits. Activate with @write.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.
uv
This project is a uv workspace with multiple members (see pyproject.toml [tool.uv.workspace]).
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.