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 rules/clubpay/ronykit/04-ronyupgit 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/04-ronyup)<a href="https://agentmods.dev/rules/clubpay/ronykit/04-ronyup"><img src="https://agentmods.dev/badge/rules/clubpay/ronykit/04-ronyup.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.00000 | $0.00580 |
| Opus 5 | $0.00000 | $0.00290 |
| Sonnet 5 | $0.00000 | $0.00116 |
| Haiku 4.5 | $0.00000 | $0.00058 |
Grade A, and why
04-ronyup 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.
What it actually says
ronyup (scaffolder + MCP server)
ronyup/ produces scaffolded app workspaces and serves the ronyup mcp knowledge/tools that drive agents. When changing how agents build apps, edit these — not AGENTS.md.
- MCP knowledge lives in
ronyup/cmd/mcp/knowledge/and is embedded + auto-loaded byloader.go(no registration needed — dropping a.mdfile is enough):server/instructions.md— always injected on MCP connect (the portable, cross-agent backbone).resources/{architecture,packages,characteristics,tools}/*.md— read on demand (knowledge://ronyup/<category>/<name>).prompts/*.md— workflow prompts (e.g.design-new-service,design-frontend).
- Bundled skills live in
ronyup/internal/skeleton/skills/<id>/SKILL.mdand must be registered inskillCatalog(ronyup/internal/scaffold/skills.go); authoring heuristic (single file vs.rules/tree) is ininternal/skeleton/skills/README.md.copySkillsships the whole directory. - Enforcement is gates and hooks, not prose (small models ignore advisory text):
ronyup/cmd/mcp/tools/scaffold/gate.go— the SRS/SDD design gate thatscaffold_featureenforces (portable across MCP clients).ronyup/internal/skeleton/backend/verify.shandinternal/skeleton/frontend/verify.sh— themake verifyquality gates (test coverage, design-doc, lint/build/stories).ronyup/internal/skeleton/workspace/.cursor/hooks/*.sh+hooks.jsontmpl— Cursorstophooks that auto-loop the agent until a gate passes.
- Keep the layers consistent. A behavior change usually touches several surfaces at once:
server/instructions.md, the relevantresources//prompts/doc,AGENTS.mdtmpl, theronykit-frameworkskill (both.agents/skills/.../SKILL.mdand the skeleton copy underronyup/internal/skeleton/workspace/.agents/skills/), andreferences/mcp-map.md. - Verify with
cd ronyup && go test ./...(the scaffold integration tests assert the generated gate/hook files exist).
Deep reference: docs/ronyup-guide.md (user-facing CLI and MCP guide).
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 · 24 lines · 0 tokens per session scan A 11b379e97c25
04-ronyup is a cursor rule published in the GitHub repository clubpay/ronykit (38 stars, last pushed 3d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 580 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.
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
git-commits
Git commit safety — commits are human-only; AI suggests, never executes.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
adapter-unit-tests
Postgres adapter unit tests are sqlmock-only; no real DB or sqlx.Connect.
studio-build
After Studio changes, regenerate embedded assets with make studio-build and keep dist in the diff.