effective_go

A set of Go coding guidelines based on Google’s Effective Go and posts from the Go team. Added to Cursor’s rules folder, it gives relevant advice while you write Go code.

In plain words
What is it for?
Use it when writing or reviewing Go code in Cursor. It helps surface guidance about Go code structure and practices.
Why use it?
It reduces the need to remember or look up common Go style and design guidance. The description does not specify how the advice is selected.

Cursor rule for Cursor

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/gabornyergesx/cursorrules/effective_go
Clone the repo
git clone --depth 1 https://github.com/gabornyergesX/cursorrules

Made for: Cursor.

Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,159 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00045 $0.04159
Opus 5 $0.00023 $0.02080
Sonnet 5 $0.00009 $0.00832
Haiku 4.5 $0.00005 $0.00416

Measured yesterday against content hash 6da96f50035c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

effective_go 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 yesterday.

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.

.cursor/rules/effective_go.mdc · 401 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

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. yesterday First seen · 401 lines · 45 tokens per session scan A 6da96f50035c

Subscribe to this mod's changes

effective_go is a cursor rule published in the GitHub repository gabornyergesX/cursorrules (1 stars, last pushed 1y ago), with no licence file. It adds 45 tokens to every session and 4,159 once invoked, about $0.0002 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-08-31.