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/inboxpraveen/minimize-cursor-cost/rubygit clone --depth 1 https://github.com/inboxpraveen/Minimize-Cursor-CostWhat 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.00380 |
| Opus 5 | $0.00000 | $0.00190 |
| Sonnet 5 | $0.00000 | $0.00076 |
| Haiku 4.5 | $0.00000 | $0.00038 |
Grade A, and why
ruby 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 yesterday.
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
Ruby / Rails Rules
Style
- Match existing style: RuboCop / Standard. Don't reformat unrelated lines.
- Match existing string-quote preference (single vs double).
- Don't add
# frozen_string_literal: trueunless other files have it.
Output
- Method change → show only the method.
- Class/module change → show only the changed methods. Use
# ... rest of class unchanged. - Don't reprint
requirelines unless adding new ones.
Rails-Specific
- Match existing controller pattern: thin controller / service objects / form objects.
- Don't add
before_actioncallbacks beyond what siblings use. - Don't add concerns or service objects unless the codebase uses them.
- Match existing Active Record style (
scopevs class methods,wherechaining vs Arel).
Migrations
- Never edit a migration that has already been run in production. Create a new one.
- Match existing migration style (
changevsup/down).
Tests
- Match existing framework: RSpec vs Minitest. Don't switch.
- For RSpec: match
describe/context/itnesting style already in the file. - Don't add
let!orbeforeblocks beyond what's needed for the new test.
Never
- Don't monkey-patch core classes.
- Don't add
attr_accessorfor things that don't need to be public. - Don't introduce metaprogramming (
define_method,method_missing) into a codebase that doesn't use it. - Don't change Gem versions unless that's the explicit task.
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.
- yesterday First seen · 39 lines · 0 tokens per session scan A 3d21bfe93a0a
ruby is a cursor rule published in the GitHub repository inboxpraveen/Minimize-Cursor-Cost (6 stars, last pushed 16d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 380 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-31.
Other cursor rules, from other repositories
sample_cursor_rule
React component best practices.
next
Next.js roof. Bundled docs for THIS next version. App vs Pages from the tree.
types
Type discipline — escape hatches are design bugs.
graphstack
GraphStack v4.7.1 — Orchestrated, graph-first, GNAP-tracked AI development (cross-platform).
55-data-model-versioning
Dataset versioning, model checkpoint management, and training reproducibility rules.
85-error-observability
Error handling, logging, and observability rules.