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/toptalentcoder/Cursor-AwesomeRulesWrote 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/toptalentcoder/cursor-awesomerules/dragonruby-error-handling)<a href="https://agentmods.dev/rules/toptalentcoder/cursor-awesomerules/dragonruby-error-handling"><img src="https://agentmods.dev/badge/rules/toptalentcoder/cursor-awesomerules/dragonruby-error-handling.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.1 | $0.00047 | $0.00047 |
| Opus 5 | $0.00023 | $0.00023 |
| Sonnet 5 | $0.00009 | $0.00009 |
| Haiku 4.5 | $0.00005 | $0.00005 |
Grade A, and why
dragonruby-error-handling 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 3d 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.
This is a copy
100% identical to dragonruby-error-handling — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
- Use exceptions for exceptional cases, not for control flow.
- Implement proper error logging and user-friendly messages.
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.
- 3d ago First seen · 6 lines · 47 tokens per session scan A b8d0b856a501
dragonruby-error-handling is a cursor rule published in the GitHub repository toptalentcoder/Cursor-AwesomeRules (6 stars, last pushed 1y ago), licensed CC0-1.0. It adds 47 tokens to every session, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to dragonruby-error-handling, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
dragonruby-best-practices-cursorrules-prompt-file
Cursor rules for DragonRuby development with best practices integration.
dragonruby-best-practices-cursorrules-prompt-file
Cursor rules for DragonRuby development with best practices integration.
dragonruby-general-ruby-rules
description: Applies general Ruby coding style, structure, and best practices for DragonRuby projects. globs: /.rb.
dragonruby-naming-conventions
description: Enforces specific naming conventions for files, methods, variables, classes, and modules in DragonRuby projects. globs: /.rb.
dragonruby-syntax-and-formatting
description: Dictates syntax and formatting guidelines for Ruby code within DragonRuby projects, adhering to the Ruby Style Guide. globs: /.rb.
dragonruby-error-handling
description: Defines error handling and validation strategies within Ruby code in DragonRuby projects. globs: /.rb.