observability-rules

A set of rules for recording application activity and checking whether services are working. Observability means collecting logs and diagnostic signals that help explain system behavior.

In plain words
What is it for?
It guides request logging, trace IDs, health checks, diagnostic output, container support for curl, and structured Python development logs.
Why use it?
It makes errors and request failures easier to trace across scripts, tests, proxies, browsers, and containers.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/dobryakov/cursor-rules/observability-rules
Clone the repo
git clone --depth 1 https://github.com/dobryakov/cursor-rules
Per session 139 This file is loaded in full into every session.
When invoked 139 The same file — it is already loaded in full.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00139 $0.00139
Opus 5 $0.00069 $0.00069
Sonnet 5 $0.00028 $0.00028
Haiku 4.5 $0.00014 $0.00014

Measured yesterday against content hash dff67671cb39, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

observability-rules scanned grade A with 1 finding 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 yesterday.

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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

* If the project contains health checks based on curl, make sure curl is included into docker image.
en/rules/observability-rules.mdc · 13 lines

What it actually says

Observability and Diagnostics

  • Use all available logs (scripts, automated tests, proxies, browser console, docker-compose) to identify the causes of errors.
  • Add diagnostic output and trace IDs to track the request flow through logs.
  • Implement health checks for key functions that are suitable for monitoring.
  • If the project contains health checks based on curl, make sure curl is included into docker image.
  • Always log incoming and outgoing HTTP requests and messages (including full body content or at least major attributes).
  • For python use structlog.dev.ConsoleRenderer() for structured logging to ensure consistent colored console output across all services for better readability during development and debugging.
Changes

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.

  1. yesterday First seen · 13 lines · 139 tokens per session scan A dff67671cb39

Subscribe to this mod's changes

observability-rules is a cursor rule published in the GitHub repository dobryakov/cursor-rules (2 stars, last pushed 2mo ago), licensed MIT. It adds 139 tokens to every session, about $0.0007 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.