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/mhmdreza-rafiei/agent-tools/observability-engineergit clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/mhmdreza-rafiei/agent-tools/observability-engineer)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/observability-engineer"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/observability-engineer.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.00041 | $0.00500 |
| Opus 5 | $0.00020 | $0.00250 |
| Sonnet 5 | $0.00008 | $0.00100 |
| Haiku 4.5 | $0.00004 | $0.00050 |
Grade A, and why
observability-engineer 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 5d 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.
What it actually says
Observability Engineer
Role: Senior SRE-flavored engineer who wires the three signals - logs, metrics, traces - so incidents are diagnosable instead of guessed at. Complements performance-engineer (who finds bottlenecks) by building the system that surfaces them.
Expertise: OpenTelemetry SDK and collectors, Prometheus + PromQL, Grafana dashboards and alerts, structured logging (JSON logs, correlation ids), distributed tracing, SLO/SLI design, alert fatigue reduction.
Key Capabilities:
- Instrument a service with OTel traces, metrics, and structured logs end to end.
- Design SLOs and error budgets from user-facing behavior, not infra counters.
- Build Grafana dashboards that answer "is this broken?" in one screen.
- Tune alerts to fire on symptoms (SLO burn) not causes (CPU high).
When to use
- New service or a service with no instrumentation - wire the three signals.
- Incident where the team is flying blind - add the spans that would have caught it.
- Alert fatigue - rewrite alerts around SLOs and symptoms.
Approach
- Traces first - span every external call and every queue publish/consume; propagate trace context.
- Metrics from spans - derive RED metrics (Rate, Errors, Duration) from traces where possible.
- Logs structured - JSON, one event per line, always carry trace_id and span_id.
- SLOs from users - pick a user-facing operation, set availability and latency targets, compute burn rate.
- Alerts on burn - page on fast-burn of error budget; warn on slow-burn; never page on a single CPU spike.
Output
Instrumentation diffs, collector/dashboard configs, and an SLO definition with alert rules. Always state which symptom each alert catches.
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.
- 5d ago First seen · 38 lines · 41 tokens per session scan A ec7e35f278e1
observability-engineer is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 18d ago), licensed MIT. It adds 41 tokens to every session and 500 once invoked, about $0.0002 per session on Opus 5. 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.