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.
git clone --depth 1 https://github.com/clubpay/ronykitWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/clubpay/ronykit/05-go-helpers)<a href="https://agentmods.dev/rules/clubpay/ronykit/05-go-helpers"><img src="https://agentmods.dev/badge/rules/clubpay/ronykit/05-go-helpers/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/clubpay/ronykit/05-go-helpers"><img src="https://agentmods.dev/badge/rules/clubpay/ronykit/05-go-helpers.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00000 | $0.00360 |
| Opus 5.5 | $0.00000 | $0.00144 |
| Sonnet 5.5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
05-go-helpers 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.
What it actually says
Shared Go helpers (x/rkit)
In a module whose go.mod requires x/rkit, use rkit before writing a small helper. Task → helper map and edge cases: x/rkit/README.md.
- if-err-panic →
rkit.Must(f())/rkit.Assert(err); nil-safe deref →rkit.PtrVal; first non-zero →rkit.Coalesce. - Collections →
rkit.Map/Filter/Reduce/Contains/ArrayToSet/MapKeysToArray/MapToArray. - Zero-copy
[]byte↔string→rkit.B2S/rkit.S2B; error-free JSON →rkit.ToJSON/rkit.FromJSON. - IDs →
rkit.RandomID(not secure;rkit.SecureRandomUint64when it must be); case →rkit.ToCamel/ToSnake/ToKebab. make lint-rkit(ronyup lint --fix) rewrites hand-written copies; depguard rejectssamber/lo,strcase, uuid/ulid/xid andjinzhu/copier. Mark a deliberate exception with//rkitcheck:ignore <reason>.- Modules without rkit in
go.mod(todayee/,std/ee/*,x/p,x/settings): use the standard library; don't add the dependency for a one-liner.
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.
- today First seen · 17 lines · 360 tokens per session scan A cabdee2ed2a7
05-go-helpers is a cursor rule published in the GitHub repository clubpay/ronykit (38 stars, last pushed yesterday), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 360 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-10-18.
Other cursor rules, from other repositories
p
Go project rules covering code style, error handling, concurrency, performance, structure, and allowed Git commands.
planning-and-delegation
Plan every task first, parallelise independent work, and staff each task with the cheapest model that can do it well.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
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.
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
shared-libraries
Shared libraries - condition framework, inventory containers, file-backed DB, itinerary, references.