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/giantswarm/muster/zz_generated.go-llm-rulesgit clone --depth 1 https://github.com/giantswarm/musterWhat 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.00342 | $0.00342 |
| Opus 5 | $0.00171 | $0.00171 |
| Sonnet 5 | $0.00068 | $0.00068 |
| Haiku 4.5 | $0.00034 | $0.00034 |
Grade A, and why
zz_generated.go-llm-rules 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 3d 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.
This is a copy
100% identical to zz_generated.go-llm-rules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
description: Go language-specific development guidelines and patterns globs: **/*.go,go.mod,go.sum
These guidelines apply to Go code and supplement any other general development instructions or workflows.
Go Code Guidelines
- All Go code is expected to adhere to the rules outlined in the Giant Swarm style guide located at @https://github.com/giantswarm/fmt/tree/main/go .
- Always fetch and fully understand the style guide before reviewing any code.
- The Giant Swarm style guide linked above must always be considered definitive. ALL rules and provisions contained in the style guide MUST be met.
- When applying the style guide, always list all instances of a particular issue, grouped by the finding type.
Formatting
CI will perform the following check for proper code formatting and sorting/grouping of imports:
go install golang.org/x/tools/cmd/goimports@latest && \
if [[ -n $(goimports -local github.com/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME} -l .) ]];
then
goimports -local github.com/${CIRCLE_PROJECT_USERNAME}/${CIRCLE_PROJECT_REPONAME} -d . && exit 1;
fi
When creating or modifying Go files, perform the according check and mitigate any issues before committing.
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.
- 3d ago First seen · 36 lines · 342 tokens per session scan A bf099bfe1ede
zz_generated.go-llm-rules is a cursor rule published in the GitHub repository giantswarm/muster (28 stars, last pushed 3d ago), licensed Apache-2.0. It adds 342 tokens to every session, about $0.0017 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to zz_generated.go-llm-rules, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
cursor-go-skills
Load the Go skills orchestrator before any Go task.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
code-style
Formatting, lint, comments language.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.
go-conventions
Go conventions for all Go code (modules, naming, errors, logging, metrics).
unit-test-coverage-95
Unit test coverage ≥95% per Go package (binding rule).