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.
git 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/rules/clubpay/ronykit/01-core)<a href="https://agentmods.dev/rules/clubpay/ronykit/01-core"><img src="https://agentmods.dev/badge/rules/clubpay/ronykit/01-core/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/rules/clubpay/ronykit/01-core"><img src="https://agentmods.dev/badge/rules/clubpay/ronykit/01-core.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00199 |
| Opus 5.5 | $0.00000 | $0.00080 |
| Sonnet 5.5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
01-core 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 1mo 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
kit / rony
kit/is the low-level core (EdgeServer, Gateway, Cluster, Service, Contract, Context).rony/is the batteries-included framework built on top of it — keep the dependency direction one-way.- Request flow:
Client -> Gateway -> northBridge -> EdgeServer -> contract lookup -> handler chain -> Response. Contexthas four storage layers: per-request, per-connection, per-service (local), cluster-wide. Use the narrowest one that works.- Routing:
RESTRouteSelector(HTTP method + path) andRPCRouteSelector(predicate) — one handler can serve both. - Read the package README before changing behavior; preserve existing architecture and naming.
Deep reference: AGENTS.md (Architecture quick reference), docs/architecture.md.
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.
- 1mo ago First seen · 16 lines · 0 tokens per session scan A b927f7385f38
01-core is a cursor rule published in the GitHub repository clubpay/ronykit (38 stars, last pushed yesterday), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 199 tokens. 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 cursor rules, from other repositories
agentic-loop
Follow this loop on every development task in this repository. For full conventions, architecture, and examples, see @.github/copilot-instructions.md (source of truth). This rule distills the workflow; do not duplicate that document.
git-commits
Git commit safety — commits are human-only; AI suggests, never executes.
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
adapter-unit-tests
Postgres adapter unit tests are sqlmock-only; no real DB or sqlx.Connect.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
studio-build
After Studio changes, regenerate embedded assets with make studio-build and keep dist in the diff.