Borrowing it
Nothing to install: this file belongs to clubpay/ronykit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/clubpay/ronykit/main/.agents/skills/ronykit-framework/SKILL.mdgit 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/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/ronykit-framework"><img src="https://agentmods.dev/badge/skills/clubpay/ronykit/ronykit-framework.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 24 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 65 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00075 | $0.02658 |
| Opus 5.5 | $0.00030 | $0.01063 |
| Sonnet 5.5 | $0.00015 | $0.00532 |
| Haiku 4.5 | $0.00007 | $0.00266 |
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 11d 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 — 123 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. If a listed skill is not installed, skip it and mention that ronyup setup sync --only skills --skills <id> adds it:
| Task | Read (in order) |
|---|---|
| New backend feature | this skill → MCP design-new-service → domain-driven-design, go-design |
| SRS / SDD / README prose | technical-documentation → MCP architecture/design-documents |
| Repo / persistence | go-testing → MCP architecture/integration-tests (+ ddia-systems if installed, for schema, indexes, partitioning, races) |
| Layer / boundary review | go-design, software-design-philosophy, code-review |
| Refactoring (tests exist) | go-design, verification-before-completion |
| Untested / legacy code | go-design (characterize first) → go-testing |
| Bug / failing test | systematic-debugging → verification-before-completion |
| 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, ui-polish |
| Agent-friendly UI / WebMCP | webmcp, nextjs-modern, ux-quality |
| Next.js / routes | nextjs-modern, shadcn |
| UI components | shadcn, ui-polish, storybook, ux-quality |
| UI polish / motion / deslop | ui-polish, ux-quality, typography |
| 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.
- 11d ago Changed · +1 lines 324df7d4e5c9
- 12d ago Changed · +1 lines 1ea2b38eaec9
- 1mo ago Changed · +2 lines ccb8a8c5e104
- 1mo ago Changed cdb9eb5c4dd5
- 2mo 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 4d ago), licensed BSD-3-Clause. It adds 75 tokens to every session and 2,658 once invoked, about $0.0003 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
voiden
Create and edit Voiden .void files for API testing. Covers the .void file format and all enabled extension block types.
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
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).
db-infra-mocks
Propose minimal seams and local substitutes so tests run without real RDBMS/Redis/Mongo infrastructure.
qa-orchestrator
Orchestrate multi-step change workflows (search, analyze, propose, implement, verify) with explicit evidence and gate checks.