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/code-formattingWrote 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/code-formatting)<a href="https://agentmods.dev/skills/clubpay/ronykit/code-formatting"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/code-formatting/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/code-formatting"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/code-formatting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00047 | $0.00704 |
| Opus 5.5 | $0.00019 | $0.00282 |
| Sonnet 5.5 | $0.00009 | $0.00141 |
| Haiku 4.5 | $0.00005 | $0.00070 |
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 23d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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
The scaffolded backend/.golangci.yml (golangci-lint v2) owns both linting
(depguard) and formatting (gofmt, gofumpt, goimports, gci). Run it
rather than the individual tools, so import grouping matches the config:
make lint # every module: golangci-lint run --fix ./...
make vet # every module: go vet ./...
cd feature/<name> && golangci-lint fmt ./... # format one module only
Treat make lint failures as blocking. A depguard error means "use the
RonyKIT equivalent" (see knowledge://ronyup/architecture/package-selection),
not "add a //nolint". Generated code (sqlc data/db, stubs) is regenerated
with make sqlc / make gen-stub, never hand-formatted.
TypeScript / JavaScript (frontend)
Use the scripts the app's package.json defines (names vary; check first):
pnpm format # Prettier (or biome) write
pnpm lint --fix # ESLint / Biome autofix
pnpm typecheck # tsc --noEmit
bash frontend/verify.sh # the full gate: typecheck, lint, build, test, stories
Prefer the formatter the repo already configures (Prettier or Biome) — do not introduce a second one.
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.
- 23d ago Changed · +10 lines e12a605e2e32
- 1mo 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 today), licensed BSD-3-Clause. It adds 47 tokens to every session and 704 once invoked, about $0.0002 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-08-30.
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…
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…
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.