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/ronykit-frameworknpx skills add clubpay/ronykit --skill ronykit-frameworkgit 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/skills/clubpay/ronykit/ronykit-framework)<a href="https://agentmods.dev/skills/clubpay/ronykit/ronykit-framework"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/ronykit-framework.svg" alt="Measured on agentmods" 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 | $0.00075 | $0.02274 |
| Opus 5 | $0.00037 | $0.01137 |
| Sonnet 5 | $0.00015 | $0.00455 |
| Haiku 4.5 | $0.00007 | $0.00227 |
Grade A, and why
ronykit-framework 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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
RonyKit (agent playbook)
Thin orchestration layer. Domain knowledge lives in the ronyup MCP server — read resources and prompts there; do not invent layout or conventions from memory.
Full MCP index: references/mcp-map.md
Prerequisites
- Confirm the
ronyupMCP server is enabled in the project (.cursor/mcp.jsonor.ai/mcp/mcp.json:commandronyup,args["mcp"]). - If MCP is unavailable, ask the user to install
ronyupand enable MCP — do not guess service structure.
Context
| Workspace | Approach |
|---|---|
RonyKit monorepo (github.com/clubpay/ronykit) |
Framework work: follow AGENTS.md / CLAUDE.md, respect go.work module boundaries. Do not scaffold into this repo unless testing ronyup. |
Scaffolded app (go.work, cmd/all-in-one, feature/) |
MCP knowledge + tools are the source of truth. Fullstack scaffolds nest the Go workspace under backend/ (run go/make/ronyup setup feature there); docs/, devops/ and AI config stay at the repo root. See architecture/workspace-layout. |
Skill routing (read SKILL.md — required)
Do not rely on memory or optional auto-discovery. Open and read .agents/skills/<id>/SKILL.md for every row that applies:
| Task | Read (in order) |
|---|---|
| New backend feature | this skill → MCP design-new-service → clean-architecture |
| Repo / persistence | go-testing → MCP architecture/integration-tests |
| Layer / boundary review | clean-architecture, code-review |
| Refactoring (tests exist) | refactoring-patterns, verification-before-completion |
| Untested / legacy code | working-with-legacy-code → go-testing → refactoring-patterns |
| Production hardening | release-it → MCP characteristics/telemetry |
| Bootstrap frontend | frontend-design, design-tokens, typography → MCP design-frontend |
| Dashboard / admin UI | dashboard-ui, shadcn, ux-quality |
| Agent-friendly UI / WebMCP | webmcp, nextjs-modern, ux-quality |
| Next.js / routes | nextjs-modern, shadcn |
| UI components | shadcn, storybook, ux-quality |
| Frontend tests | frontend-testing, verification-before-completion |
| Before claiming done | verification-before-completion, code-formatting |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 119 lines · 75 tokens per session scan A acf6a8e779ed
ronykit-framework is a skill published in the GitHub repository clubpay/ronykit (38 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 75 tokens to every session and 2,274 once invoked, about $0.0004 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
sql-database-support
Guides classifying, gap-analyzing, and scaffolding support for a new SQL database in pREST (wire-compatible variants like TimescaleDB or new dialects). Use when adding database support, creating integration/ /, DIFFERENCES.md, adapters/ , per-DB docker-compose or GitHub workflows, or planning where config/app wiring…
prest-integration-tests
Guides writing and reviewing pREST Docker/network integration tests under integration/ so each request is human-readable via step comments or table-driven descriptions. Use when adding or editing integration//test.go, HTTP controller E2E coverage, make test-integration, test-integration-postgres…
ast-introspection
Use Go AST-aware analysis to enumerate symbols, extract signatures, and propose mechanically safe refactors (read-only by default).
build-run
Build and run the project locally to reproduce compile/runtime issues in a safe, non-production way.
ci-orchestrator
Run a CI-like pipeline locally (format, lint, vet, static-analysis, tests) and summarize per-step results with remediation guidance.
config-loader-helper
Diagnose configuration-related failures, enumerate required env vars, and guide safe local test setup (no secrets).