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.
npx agentmods add rules/matank001/cursor-security-rules/secure-dev-golanggit clone --depth 1 https://github.com/matank001/cursor-security-rulesWhat 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 | $0.00000 | $0.02384 |
| Opus 5 | $0.00000 | $0.01192 |
| Sonnet 5 | $0.00000 | $0.00477 |
| Haiku 4.5 | $0.00000 | $0.00238 |
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" 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/gobfor 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)
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.
- 2d ago First seen · 269 lines · 2,384 tokens per session scan C e533c25cd267
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.
Other cursor rules, from other repositories
ankra-cli
Ankra CLI rules and best practices for managing Kubernetes clusters via the Ankra platform.
go-backend-scalability-cursorrules-prompt-file
Cursor rules for Go development with backend scalability.
cloudflare-email-telegram-cursorrules-prompt-file
Cursor rules for setting up email-to-Telegram forwarding via Cloudflare Email Routing and Workers using the mail2tg CLI.
flutter-riverpod-cursorrules-prompt-file
Cursor rules for Flutter Riverpod.
angular-novo-elements-cursorrules-prompt-file
Cursor rules for Angular development with Novo Elements UI library.
automl-hyperparameter-optimization
AutoML and hyperparameter optimization rules for Python ML projects using Ray Tune, Optuna, PyCaret, and time-series AutoML libraries.