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/tyrchen/cursor-rust-rules/error-handlinggit clone --depth 1 https://github.com/tyrchen/cursor-rust-rulesWhat 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.02950 |
| Opus 5 | $0.00000 | $0.01475 |
| Sonnet 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 2d 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.
- 2d 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
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.