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/tyrchen/cursor-rust-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/tyrchen/cursor-rust-rules/error-handling)<a href="https://agentmods.dev/rules/tyrchen/cursor-rust-rules/error-handling"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/error-handling/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/tyrchen/cursor-rust-rules/error-handling"><img src="https://agentmods.dev/badge/rules/tyrchen/cursor-rust-rules/error-handling.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.02950 |
| Opus 5.5 | $0.00000 | $0.01180 |
| Sonnet 5.5 | $0.00000 | $0.00590 |
| Haiku 4.5 | $0.00000 | $0.00295 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🚨 RUST ERROR HANDLING STANDARDS
TL;DR: Comprehensive error handling guidelines using thiserror for libraries and anyhow for binaries, with centralized error definitions per crate.
🔍 ERROR HANDLING STRATEGY SELECTION
graph TD
Project["Project Analysis"] --> CrateType{"Crate Type?"}
CrateType -->|"lib"| LibCrate["Library Crate"]
CrateType -->|"bin"| BinCrate["Binary Crate"]
LibCrate --> ThiserrorChoice["Use thiserror"]
BinCrate --> AnyhowChoice["Use anyhow"]
ThiserrorChoice --> LibFeatures["Library Features:"]
AnyhowChoice --> BinFeatures["Binary Features:"]
LibFeatures --> Structured["• Structured errors"]
LibFeatures --> Derived["• Derive Error trait"]
LibFeatures --> Transparent["• Error forwarding"]
LibFeatures --> Documentation["• Error documentation"]
BinFeatures --> Simple["• Simple error handling"]
BinFeatures --> Context["• Rich context"]
BinFeatures --> Chaining["• Error chaining"]
BinFeatures --> EndUser["• End-user messages"]
style Project fill:#4da6ff,stroke:#0066cc,color:white
style CrateType fill:#ffa64d,stroke:#cc7a30,color:white
style LibCrate fill:#4dbb5f,stroke:#36873f,color:white
style BinCrate fill:#d94dbb,stroke:#a3378a,color:white
📚 LIBRARY CRATE ERROR HANDLING (thiserror)
Error Definition Pattern
// lib_crate/src/errors.rs
use thiserror::Error;
#[derive(Error, Debug)]
pub enum MyLibError {
#[error("Invalid input: {message}")]
InvalidInput { message: String },
#[error("File not found: {path}")]
FileNotFound { path: String },
#[error("Permission denied")]
PermissionDenied,
#[error("Network error")]
Network(#[from] reqwest::Error),
#[error("IO error")]
Io(#[from] std::io::Error),
#[error("Parse error: {0}")]
Parse(#[from] serde_json::Error),
#[error("Configuration error: {message}")]
Config { message: String },
#[error("Internal error: {0}")]
Internal(String),
}
// Additional result type alias for convenience
pub type Result<T> = std::result::Result<T, MyLibError>;
// Error construction helpers
impl MyLibError {
pub fn invalid_input(message: impl Into<String>) -> Self {
Self::InvalidInput {
message: message.into(),
}
}
pub fn file_not_found(path: impl Into<String>) -> Self {
Self::FileNotFound {
path: path.into(),
}
}
pub fn config(message: impl Into<String>) -> Self {
Self::Config {
message: message.into(),
}
}
pub fn internal(message: impl Into<String>) -> Self {
Self::Internal(message.into())
}
}
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 · 485 lines · 0 tokens per session scan A 8ab864c6ff76
error-handling is a cursor rule published in the GitHub repository tyrchen/cursor-rust-rules (27 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,950 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
rust-module-refactor
Use when splitting Rust modules, moving tests, tightening visibility, or preserving facades during refactors.
rust-architect
PoolAI — Rust Architect workflow: runtime stack, MSYS2, target/ disk, pre-push checks, docs sync.
table-of-contents-standard
Standard section ordering and TOC format for Verus source files.
arc-deref-pattern
When implementing parallel (Mt) algorithms in Verus, do NOT assume.
wrap-vs-specify
When to use externaltypespecification vs wrapper struct for Verus specs.
core
Core STT/TTS abstraction layer documentation.