Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/clubpay/ronykitnpx agentmods add skills/clubpay/ronykit/go-designWrote 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/skills/clubpay/ronykit/go-design)<a href="https://agentmods.dev/skills/clubpay/ronykit/go-design"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/go-design/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/skills/clubpay/ronykit/go-design"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/go-design.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.00129 | $0.03281 |
| Opus 5.5 | $0.00052 | $0.01312 |
| Sonnet 5 | $0.00026 | $0.00656 |
| Haiku 4.5 | $0.00013 | $0.00328 |
Grade A, and why
go-design 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.
How it starts
The opening of the file, as written. The whole thing — 261 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Go Design
Go has packages, structs, functions, and implicitly satisfied interfaces — no classes, no inheritance, no overriding. Most class-based design advice either translates into something simpler or doesn't apply. This skill keeps the ideas that survive the translation and states them in Go terms.
When to use
- Deciding where code goes in a feature module, or reviewing a PR that crosses layers.
- Designing a package, an interface, or a constructor.
- Refactoring: a smell is slowing you down and tests are green.
- A book, blog, or habit suggests a class hierarchy and you need the Go shape.
- Changing code that has no tests (legacy code is simply code without tests).
1. Dependency direction
Business rules must not depend on delivery or storage details. In a RonyKit feature module the direction is fixed:
| Package | Owns | May import |
|---|---|---|
api/ |
Rony contract, DTOs (json tags), request → call → response mapping |
internal/app, internal/domain, rony |
internal/app |
Use cases as *App methods; interfaces it consumes |
internal/domain, internal/repo (ports), rony/errs |
internal/domain |
Types, invariants, rules, sentinel errors | stdlib, rony/errs, x/rkit |
internal/repo (port.go) |
Repository interfaces in domain types | internal/domain |
internal/repo/v0 |
sqlc implementation; row ↔ domain mapping | internal/repo, internal/domain, sqlc output |
module.go / service.go |
fx wiring: the only place concrete adapters meet | everything above |
- Data crosses boundaries as domain types or plain values — never sqlc rows,
DTOs, or
*RContext. - The
ronypackage (contexts, routes) stays inapi/and wiring;rony/errsis fine everywhere. - Other feature modules are reached through generated stubs, never by
importing their
internal/. - Keep the handler humble: decode, call one
Appmethod, map the result. What is hard to test (transport) stays thin; what matters (rules) is testable without it.
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.
- yesterday First seen · 261 lines · 129 tokens per session scan A 4d3b742870a6
go-design is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed 2d ago), licensed BSD-3-Clause. It adds 129 tokens to every session and 3,281 once invoked, about $0.0005 per session on Opus 5.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-09-26.
Other skills, from other repositories
pr-to-go-linter
Generate a new pkg/linters analyzer from a merged or open PR pattern.
golang-refactoring
Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, gofmt -r, gopatch), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code…
go-concurrency-safety
L1 supplement - audits Go-specific concurrency hazards in node client code: map iteration non-determinism, goroutine leaks, mutex ordering, panic boundaries, context cancellation.
design-review
Deep design review of Go codebase — naming, structure, consistency, interfaces, error handling. Scores each dimension and provides actionable fixes.
agents-md
Generate AGENTS.md files for Go, Rust, TypeScript, and Java projects. Use this skill whenever the user asks to create, scaffold, bootstrap, update, or review an AGENTS.md (or agent-instructions, CLAUDE.md, repo guide for agents) file in a codebase. Also trigger when the user says "add AGENTS.md", "make this repo…
ring:verifying-code
Verifying a Go project: runs every quality check (lint, vet, imports, format, docs, unit, integration, E2E) and returns a single MERGEREADY or NEEDSFIX verdict. Report-only: never fixes anything. Use for a quick pre-merge or pre-PR check outside a full dev-cycle. Skip when not a Go project, when you want a single…