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/observabilitygit 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.05084 |
| Opus 5 | $0.00000 | $0.02542 |
| Sonnet 5 | $0.00000 | $0.01017 |
| Haiku 4.5 | $0.00000 | $0.00508 |
Grade A, and why
observability 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 โ 773 lines โ stays where its author put it; the contents beside it link to each section on GitHub.
๐ RUST OBSERVABILITY PATTERNS
TL;DR: Comprehensive observability patterns for Rust applications, including lock-free metrics collection, distributed tracing, health checks, and monitoring integration.
๐ OBSERVABILITY STRATEGY
graph TD
Start["Observability Needs"] --> MetricsQ{"Metrics<br>Required?"}
Start --> TracingQ{"Distributed<br>Tracing?"}
Start --> HealthQ{"Health<br>Checks?"}
MetricsQ -->|Yes| MetricsType{"Metrics<br>Type?"}
MetricsType -->|Counters| Counters["Lock-free Counters"]
MetricsType -->|Histograms| Histograms["Response Time Tracking"]
MetricsType -->|Gauges| Gauges["Current State Metrics"]
TracingQ -->|Yes| TracingType{"Tracing<br>Scope?"}
TracingType -->|Application| AppTracing["Application Tracing"]
TracingType -->|Distributed| DistTracing["Distributed Tracing"]
HealthQ -->|Yes| HealthType{"Health Check<br>Type?"}
HealthType -->|Simple| SimpleHealth["Basic Health Checks"]
HealthType -->|Complex| ComplexHealth["Dependency Health Checks"]
Counters --> Collection["Metrics Collection"]
Histograms --> Collection
Gauges --> Collection
AppTracing --> TracingCollection["Trace Collection"]
DistTracing --> TracingCollection
SimpleHealth --> HealthCollection["Health Monitoring"]
ComplexHealth --> HealthCollection
Collection --> Export["Export & Integration"]
TracingCollection --> Export
HealthCollection --> Export
Export --> Production["Production Observability"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style Counters fill:#4dbb5f,stroke:#36873f,color:white
style AppTracing fill:#ffa64d,stroke:#cc7a30,color:white
style SimpleHealth fill:#d94dbb,stroke:#a3378a,color:white
๐ฏ METRICS COLLECTION PATTERNS
Lock-Free Metrics for High Performance
use std::sync::atomic::{AtomicU64, Ordering};
use std::sync::Arc;
use dashmap::DashMap;
use prometheus::{Counter, Histogram, Gauge, Registry, Opts, HistogramOpts};
// โ
Lock-free atomic counter for high-throughput scenarios
#[derive(Debug)]
pub struct AtomicCounter {
value: AtomicU64,
}
impl AtomicCounter {
pub fn new() -> Self {
Self {
value: AtomicU64::new(0),
}
}
pub fn increment(&self) -> u64 {
self.value.fetch_add(1, Ordering::Relaxed)
}
pub fn add(&self, value: u64) -> u64 {
self.value.fetch_add(value, Ordering::Relaxed)
}
pub fn get(&self) -> u64 {
self.value.load(Ordering::Relaxed)
}
pub fn reset(&self) -> u64 {
self.value.swap(0, Ordering::Relaxed)
}
}
impl Default for AtomicCounter {
fn default() -> Self {
Self::new()
}
}
// โ
Comprehensive metrics collector
pub struct MetricsCollector {
counters: DashMap<String, Arc<AtomicCounter>>,
prometheus_counters: DashMap<String, Counter>,
prometheus_histograms: DashMap<String, Histogram>,
prometheus_gauges: DashMap<String, Gauge>,
registry: Registry,
}
impl MetricsCollector {
pub fn new() -> Self {
Self {
counters: DashMap::new(),
prometheus_counters: DashMap::new(),
prometheus_histograms: DashMap::new(),
prometheus_gauges: DashMap::new(),
registry: Registry::new(),
}
}
/// Get or create a counter
pub fn counter(&self, name: &str) -> Arc<AtomicCounter> {
self.counters
.entry(name.to_string())
.or_insert_with(|| Arc::new(AtomicCounter::new()))
.clone()
}
/// Get or create a Prometheus counter
pub fn prometheus_counter(&self, name: &str, help: &str) -> Result<Counter, MetricsError> {
if let Some(counter) = self.prometheus_counters.get(name) {
return Ok(counter.clone());
}
let opts = Opts::new(name, help);
let counter = Counter::with_opts(opts)?;
self.registry.register(Box::new(counter.clone()))?;
self.prometheus_counters.insert(name.to_string(), counter.clone());
Ok(counter)
}
/// Get or create a Prometheus histogram
pub fn prometheus_histogram(&self, name: &str, help: &str, buckets: Vec<f64>) -> Result<Histogram, MetricsError> {
if let Some(histogram) = self.prometheus_histograms.get(name) {
return Ok(histogram.clone());
}
let opts = HistogramOpts::new(name, help).buckets(buckets);
let histogram = Histogram::with_opts(opts)?;
self.registry.register(Box::new(histogram.clone()))?;
self.prometheus_histograms.insert(name.to_string(), histogram.clone());
Ok(histogram)
}
/// Get or create a Prometheus gauge
pub fn prometheus_gauge(&self, name: &str, help: &str) -> Result<Gauge, MetricsError> {
if let Some(gauge) = self.prometheus_gauges.get(name) {
return Ok(gauge.clone());
}
let opts = Opts::new(name, help);
let gauge = Gauge::with_opts(opts)?;
self.registry.register(Box::new(gauge.clone()))?;
self.prometheus_gauges.insert(name.to_string(), gauge.clone());
Ok(gauge)
}
/// Export metrics in Prometheus format
pub fn export_prometheus(&self) -> Result<String, MetricsError> {
use prometheus::Encoder;
let encoder = prometheus::TextEncoder::new();
let metric_families = self.registry.gather();
let mut buffer = Vec::new();
encoder.encode(&metric_families, &mut buffer)?;
Ok(String::from_utf8(buffer)?)
}
/// Get all counter values as a snapshot
pub fn counter_snapshot(&self) -> std::collections::HashMap<String, u64> {
self.counters
.iter()
.map(|entry| (entry.key().clone(), entry.value().get()))
.collect()
}
}
impl Default for MetricsCollector {
fn default() -> Self {
Self::new()
}
}
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 ยท 773 lines ยท 0 tokens per session scan A adf71532f437
observability 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 5,084 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.