go-api-security-and-best-practices

go-api-security-and-best-practices is a cursor rule for Cursor from paulpham157/paul-s-cursor-rules. It costs 0 tokens per session (134 once invoked), scanned A, original, MIT.

A set of guidelines for building secure and maintainable web APIs in Go, a programming language. It covers validation, authentication, logging, rate limiting, and REST design.

In plain words
What is it for?
It is for designing and implementing Go API endpoints, middleware, request handling, logging, and access controls.
Why use it?
It helps avoid common API problems such as accepting unsafe input, exposing unauthorised data, poor error tracking, and uncontrolled traffic.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

Good fit It is for designing and implementing Go API endpoints, middleware, request handling, logging, and access controls.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/paulpham157/paul-s-cursor-rules/go-api-security-and-best-practices
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/paulpham157/paul-s-cursor-rules

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-api-security-and-best-practices

README.md
[![agentmods](https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/go-api-security-and-best-practices/github.svg)](https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/go-api-security-and-best-practices)
Your own site
<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/go-api-security-and-best-practices"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/go-api-security-and-best-practices/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-api-security-and-best-practices

Your own site · 80×15
<a href="https://agentmods.dev/rules/paulpham157/paul-s-cursor-rules/go-api-security-and-best-practices"><img src="https://agentmods.dev/badge/rules/paulpham157/paul-s-cursor-rules/go-api-security-and-best-practices.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 134 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.00000 $0.00134
Opus 5 $0.00000 $0.00067
Sonnet 5 $0.00000 $0.00027
Haiku 4.5 $0.00000 $0.00013

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

Security

Grade A, and why

go-api-security-and-best-practices 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 5d 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

Copies of this mod

2 near-identical copies found in the catalogue:

1/framework_rules/rules/go-servemux-rest-api-cursorrules-prompt-file/go-api-security-and-best-practices.mdc · 11 lines

What it actually says

  • Implement input validation for API endpoints.
  • Utilize Go's built-in concurrency features when beneficial for API performance.
  • Follow RESTful API design principles and best practices.
  • Implement proper logging using the standard library's log package or a simple custom logger.
  • Consider implementing middleware for cross-cutting concerns (e.g., logging, authentication).
  • Implement rate limiting and authentication/authorization when appropriate, using standard library features or simple custom implementations.
  • Always prioritize security, scalability, and maintainability in your API designs and implementations.
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. 5d ago First seen · 11 lines · 0 tokens per session scan A f4a05332cda1

Subscribe to this mod's changes

go-api-security-and-best-practices is a cursor rule published in the GitHub repository paulpham157/paul-s-cursor-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 134 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-09-03.