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 skills/clubpay/ronykit/code-reviewnpx skills add clubpay/ronykit --skill code-reviewgit clone --depth 1 https://github.com/clubpay/ronykitWhat 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.00047 | $0.00877 |
| Opus 5 | $0.00023 | $0.00439 |
| Sonnet 5 | $0.00009 | $0.00175 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
code-review 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Review for correctness and design first, style last (a formatter owns style). Prioritize feedback so the important things aren't lost in nits.
When to use
- Reviewing a teammate's PR or diff.
- Self-reviewing your own change before requesting review.
- Deciding whether a change is safe to merge.
What to check, in priority order
- Correctness — does it do what it claims? Edge cases, error paths, off-by-one, nil/empty, concurrency, boundary conditions.
- Security & safety — input validation, authz checks, injection, secrets in code/logs, unsafe defaults.
- Design fit — right layer/abstraction; follows existing architecture and
package-selection rules; no leaking concerns across boundaries. For RonyKit
features, read
clean-architecture— handlers thin, logic ininternal/app, persistence behindinternal/repo/port.go. - Tests — meaningful tests for new behavior and fixed bugs; deterministic; assert behavior not internals.
- Readability — clear names, small functions, comments only where intent is non-obvious.
- Style — defer to the formatter/linter; don't hand-review spacing.
Watch for over-engineering
Complexity is a cost, not a credential. Flag code built to impress (or "just in case") rather than to meet a real requirement — it compounds maintenance with no user value. Quick lenses:
- Deletion test — if this were removed, who'd notice and when? "Only the author" means it's not pulling its weight.
- Abstraction needs ≥3 uses — one implementation behind an interface is indirection, not abstraction. Don't add a layer for a hypothetical second case.
- Scale is actual, not imagined — generality/caching/sharding for traffic you don't have is speculation; prefer the simplest thing that fits today.
- Dependencies earn their keep — a new library must save more than its
footprint and upgrade burden; prefer a workspace helper (
x/*,rony/*). - Premature optimization — no micro-optimizations without a measurement; readable beats clever on cold paths.
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.
- 2d ago First seen · 86 lines · 47 tokens per session scan A 5f07bc91f87c
code-review is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 47 tokens to every session and 877 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-30.
Other skills, from other repositories
procedure
Vovk.ts procedures — atomic unit of server-side logic in Vovk project. Use whenever user asks to build ANYTHING producing or consuming data on server — page loading data ("users page", "dashboard", "product list"), endpoint, API handler, server action, form submission, controller, validation with Zod / Valibot /…
rpc
Vovk.ts RPC client — how vovk generate turns controllers into type-safe client modules, composed vovk-client vs segmented clients, call shape (apiRoot, params, body, query, meta, init, disableClientValidation, validateOnClient, interpretAs, transform, fetcher), customizing generation via outputConfig.imports.fetcher +…
tools
Building LLM tools with Vovk.ts — deriveTools() (procedures → tools), createTool() (standalone tools, no controller/procedure needed), @operation.tool({ name, title, description, hidden }) decorator, x-tool metadata, ToModelOutput.DEFAULT vs ToModelOutput.MCP formatters, the tools + toolsByName return shape, the meta…
mixins
Vovk.ts OpenAPI mixins — importing third-party OpenAPI 3.x schemas as typed client modules that share the same call signature as native Vovk RPC modules. Use whenever the user asks to "call a third-party API from my Vovk app", "mixin an OpenAPI schema", "import an OpenAPI spec as a client", "wrap an external service…
bundle
Vovk.ts vovk bundle CLI — packages composed TypeScript client as zero-dep publishable npm package. Covers bundle.build async fn, [email protected] recipe, outputConfig.origin / package / reExports / imports.validateOnClient: null, prebundleOutDir / outDir / keepPrebundleDir, --include/--exclude segments, --openapi- mixin…
decorators
Vovk.ts decorators — built-in (@prefix, @operation, @get/@post/@put/@patch/@del, .auto()) and custom via createDecorator. Covers authorization / auth decorators, middleware-style wrapping (pre-handler + post-handler logic), req.vovk.meta() for cross-decorator state, stacking order, the decorate() alternative for…