secure-dev-golang

Security rules for Go programs, including services, command-line tools, request handlers, and background jobs. They focus on safely processing outside data and choosing safer defaults.

In plain words
What is it for?
Use them when creating or reviewing Go code that reads requests, parses JSON, YAML, protocol messages, or other untrusted data.
Why use it?
They help prevent vulnerabilities caused by unsafe decoding, oversized input, unknown fields, and other unsafe handling of data from outside the program.

Cursor rule

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.

agentmods
npx agentmods add rules/matank001/cursor-security-rules/secure-dev-golang
Clone the repo
git clone --depth 1 https://github.com/matank001/cursor-security-rules
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,384 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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 $0.00000 $0.02384
Opus 5 $0.00000 $0.01192
Sonnet 5 $0.00000 $0.00477
Haiku 4.5 $0.00000 $0.00238

Measured 2d ago against content hash e533c25cd267, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

secure-dev-golang scanned grade C with 1 finding 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 2d 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.

Reaches for credential fileshighPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

// userPath like "../../etc/shadow"
secure-dev-golang.mdc · 269 lines

How it starts

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

These rules apply to all Go code in the repository (CLI tools, services, handlers, background jobs) and aim to prevent common security risks through disciplined input handling, safe APIs, and secure defaults.

All violations must include a clear explanation of which rule was triggered and why, so developers can fix issues quickly.
Generated code must not violate these rules. If a rule is violated, add a code comment that explains the problem and proposes a correction.

1. Decode Untrusted Data Safely

  • Rule: Do not deserialize untrusted data with unsafe or permissive decoders. Prefer strict JSON or protobuf with size limits. Reject unknown fields. Avoid encoding/gob for untrusted input. Use strict YAML decoding only if required.
  • Unsafe:
    // Accepts arbitrarily large input and unknown fields
    var in any
    _ = json.NewDecoder(r.Body).Decode(&in)
    
  • Safe:
    type CreateUser struct {
        Name  string `json:"name"`
        Email string `json:"email"`
    }
    
    dec := json.NewDecoder(http.MaxBytesReader(w, r.Body, 1<<20)) // 1 MB cap
    dec.DisallowUnknownFields()
    dec.UseNumber()
    
    var in CreateUser
    if err := dec.Decode(&in); err != nil { /* handle */ }
    
  • YAML (only if needed):
    dec := yaml.NewDecoder(bytes.NewReader(b))
    dec.KnownFields(true) // yaml.v3
    if err := dec.Decode(&cfg); err != nil { /* handle */ }
    
  • Protobuf JSON:
    opts := protojson.UnmarshalOptions{DiscardUnknown: false}
    if err := opts.Unmarshal(b, msg); err != nil { /* handle */ }
    

2. Use Parameterized Queries for Database Access

  • Rule: Never format SQL with user input. Use placeholders and arguments. Use context with timeouts.
  • Unsafe:
    query := fmt.Sprintf("SELECT * FROM users WHERE name = '%s'", name)
    rows, _ := db.Query(query)
    
  • Safe:
    ctx, cancel := context.WithTimeout(r.Context(), 3*time.Second)
    defer cancel()
    
    row := db.QueryRowContext(ctx, "SELECT id FROM users WHERE name = $1", name)
    

Read the full file on GitHub · 269 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. 2d ago First seen · 269 lines · 2,384 tokens per session scan C e533c25cd267

Subscribe to this mod's changes

secure-dev-golang is a cursor rule published in the GitHub repository matank001/cursor-security-rules (378 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,384 tokens. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.