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/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)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/observability"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/observability/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/mhmdreza-rafiei/agent-tools/observability"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/observability.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.00021 | $0.00408 |
| Opus 5 | $0.00010 | $0.00204 |
| Sonnet 5 | $0.00004 | $0.00082 |
| Haiku 4.5 | $0.00002 | $0.00041 |
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 8d 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
Applies when adding or changing a path that runs in production (endpoints, jobs, queues, workers). Load for new services, hot-path changes, incident prep. Not every chat.
Logs
- Structured logs (JSON), not free-text lines. A log entry has: timestamp, level, event, request_id, and the relevant IDs (user, tenant, order).
- Log at the boundaries (in / out / error), not every line inside.
- Never log secrets or PII. Redact before logging.
- Levels mean what they say:
erroris actionable,warnis suspicious,infois a normal event. Don'tinfo-spam.
Metrics
- Counters for events (requests, errors, retries); histograms for distributions (latency, payload size); gauges for current state (queue depth, in-flight requests).
- Label by route / status / tenant — enough to slice, not so much that cardinality explodes.
Tracing
- One span per unit of work (one request, one queue job, one DB call).
- Propagate the trace context across service boundaries (W3C traceparent).
- The span name is the operation, not the URL (
"create_order", not"/v1/orders").
The three together
- A user reports a slow checkout. Logs find the error; metrics show it's p99 not median; traces show which downstream is the bottleneck. Build for that query.
Do not
- Add a log line per loop iteration.
- Use
print/console.logfor production observability. - Ship an endpoint with no request_id — you can't correlate its logs.
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.
- 8d ago First seen · 48 lines · 21 tokens per session scan A f356cb73f6b8
observability is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 24d ago), licensed MIT. It adds 21 tokens to every session and 408 once invoked, about $0.0001 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-09-03.
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.