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-formattingnpx skills add clubpay/ronykit --skill code-formattinggit 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.00493 |
| Opus 5 | $0.00023 | $0.00246 |
| Sonnet 5 | $0.00009 | $0.00099 |
| Haiku 4.5 | $0.00005 | $0.00049 |
Grade A, and why
code-formatting 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.
What it actually says
Code Formatting & Linting
Formatting is not opinion — run the tool and move on. Never hand-format what a formatter owns. Always finish a change with formatters and linters clean.
When to use
- Right before declaring an edit complete.
- A CI or local lint/format check failed.
- Touching a file whose formatting drifted.
Principles
- Let tools decide style. Don't argue spacing/quotes/imports — run the formatter.
- Format only what you touched unless a repo-wide reformat is explicitly requested; avoid unrelated churn in diffs.
- Lint failures are signal. A
depguard/import-rule failure is a design violation (wrong dependency), not a nit — fix the import, don't suppress it. - Don't blanket-disable rules. Narrow, justified
//nolint/eslint-disablewith a reason only when truly warranted.
Go
gofmt -w . # or: go fmt ./...
goimports -w . # group/order imports
go vet ./...
golangci-lint run # repo lint config (depguard, etc.)
In this workspace, make lint runs the configured linters; treat its failures
as blocking. Forbidden-import errors mean "use the RonyKIT equivalent".
TypeScript / JavaScript (frontend)
pnpm format # Prettier (or biome) write
pnpm lint --fix # ESLint / Biome autofix
pnpm typecheck # tsc --noEmit
Prefer the formatter the repo already configures (Prettier or Biome) — do not introduce a second one.
Markdown
make format-md # repo Markdown formatter (preserves YAML frontmatter)
Checklist before "done"
- Formatter run on changed files; diff contains no stray reformatting.
- Linter and type checker pass (or only pre-existing, unrelated failures remain).
- No new broad lint suppressions.
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 · 65 lines · 47 tokens per session scan A 598139fe2924
code-formatting 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 493 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…