go

Go conventions for all Zapstore Go projects (zsp, server, zindex, zapstore-cli).

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/zapstore/zsp/go
Clone the repo
git clone --depth 1 https://github.com/zapstore/zsp

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 635 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00635
Opus 5 $0.00000 $0.00318
Sonnet 5 $0.00000 $0.00127
Haiku 4.5 $0.00000 $0.00064

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

Security

Grade A, and why

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 today.

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/go.mdc · 63 lines

How it starts

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

Go Conventions

Style

  • Standard library style. Run gofmt. No third-party linters beyond go vet.
  • Use internal/ for private packages. Public API surface should be minimal.
  • Prefer flat package structure within internal/ — one package per concern, not deep nesting.
  • Reference existing patterns in the same project before inventing new ones.

Error Handling

  • Wrap errors with fmt.Errorf("context: %w", err) — always add context.
  • Return errors; don't panic. Panics are only acceptable for programmer bugs (unreachable code).
  • Use errors.Is / errors.As for sentinel and typed error checks.
  • Define sentinel errors as package-level var ErrFoo = errors.New("foo").

Testing

  • Table-driven tests. Name subtests clearly.
  • Test files live next to the code they test (foo_test.go beside foo.go).
  • Use testdata/ for fixtures.
  • No test frameworks — standard testing package only.

Dependencies

  • Prefer the standard library. Add a dependency only when it saves significant complexity.
  • All projects use github.com/nbd-wtf/go-nostr for Nostr operations.
  • Pin dependency versions via go.sum. Run go mod tidy after changes.

Concurrency

  • Use context.Context for cancellation. Pass it as the first parameter.
  • Prefer sync.WaitGroup or errgroup.Group over bare goroutines.
  • No goroutine leaks — every goroutine must have a clear shutdown path.
  • Use channels for communication, mutexes for state protection. Don't mix.

Naming

  • Short, clear names. src not sourceManager. cfg not configuration.
  • Interfaces describe behavior: Signer, Publisher, not ISignerInterface.
  • Acronyms are all-caps: URL, HTTP, APK, ID.

Project Layout

  • main.go — entry point, minimal logic, delegates to internal/.
  • internal/ — all business logic, one package per domain.
  • testdata/ — test fixtures, config examples.
  • Makefile — build commands where applicable.

Build

  • Use -ldflags for version injection at build time.
  • Support go install module@latest with embedded build info fallback.
  • CGo is acceptable where needed (e.g. SQLite) but prefer pure Go when possible.
  • make (default build target) produces a single binary named after the project at the repo root.
  • make all cross-compiles for all supported platforms into dist/ as <binary>-<os>-<arch>.
  • Always pass -trimpath -ldflags '-s -w' for reproducible, stripped binaries.

Read the full file on GitHub · 63 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. today First seen · 63 lines · 0 tokens per session scan A 0fe6c1ef4b30

Subscribe to this mod's changes

go is a cursor rule published in the GitHub repository zapstore/zsp (18 stars, last pushed 28d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 635 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-01.