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/rodrigovilina/ruby_cursor_rulesWrote 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/rodrigovilina/ruby_cursor_rules/ruby-testing-conventions)<a href="https://agentmods.dev/rules/rodrigovilina/ruby_cursor_rules/ruby-testing-conventions"><img src="https://agentmods.dev/badge/rules/rodrigovilina/ruby_cursor_rules/ruby-testing-conventions/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/rodrigovilina/ruby_cursor_rules/ruby-testing-conventions"><img src="https://agentmods.dev/badge/rules/rodrigovilina/ruby_cursor_rules/ruby-testing-conventions.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.00011 | $0.00692 |
| Opus 5.5 | $0.00004 | $0.00277 |
| Sonnet 5.5 | $0.00002 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
Grade A, and why
ruby-testing-conventions 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 2mo 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2mo ago First seen · 102 lines · 11 tokens per session scan A a97d2ad3e666
ruby-testing-conventions is a cursor rule published in the GitHub repository rodrigovilina/ruby_cursor_rules (2 stars, last pushed 1y ago), with no licence file. It adds 11 tokens to every session and 692 once invoked, about $0.0000 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-31.
Other cursor rules, from other repositories
production-code
Production code rule — TDD precondition + Spring Boot 4 conventions.
test-code
Test code rule — JUnit 5, Testcontainers, traceability tagging.
rspec-let-do-blocks
Cursor rule "rspec-let-do-blocks" from panozzaj/cursor-rules, covering multi-line array, multi-line method call with keyword args, multi-line hash definition, complex single line expression and using { ... } for multi-line blocks.
typescript
You are an expert in building MCP servers in TypeScript using a test-driven design methodology.
vitest-expect-typeof
The toMatchTypeOf() matcher has been deprecated in Vitest's expectTypeOf API.
python-testing
This rule provides comprehensive guidance for testing Python applications before production deployment. It covers test-driven development (TDD), different types of tests, using both mock and real data, and implementing testing loops to ensure code quality.