speckit.sre-observability

speckit.sre-observability is a skill for Claude Code, Codex from wedabro/bro-skills. It costs 32 tokens per session (926 once invoked), scanned A, original, MIT.

A guide for adding observability and site reliability practices to services. It covers OpenTelemetry tracing, Prometheus metrics, structured logs, alerts, and resilience controls.

In plain words
What is it for?
Use it to plan telemetry across HTTP, gRPC, queues, databases, background jobs, and caches. It also helps configure monitoring and resilience in Docker or Kubernetes deployments.
Why use it?
It helps teams see what services are doing and find failures across connected systems. It also provides checks for reliability targets and failure handling.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

Good fit Use it to plan telemetry across HTTP, gRPC, queues, databases, background jobs, and caches. It also helps configure monitoring and resilience in Docker or Kubernetes deployments.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/wedabro/bro-skills/speckit.sre-observability
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.

Any agent
npx skills add wedabro/bro-skills --skill speckit.sre-observability
Clone the repo
git clone --depth 1 https://github.com/wedabro/bro-skills

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for speckit.sre-observability

README.md
[![agentmods](https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.sre-observability/github.svg)](https://agentmods.dev/skills/wedabro/bro-skills/speckit.sre-observability)
Your own site
<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.sre-observability"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.sre-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.

agentmods 80×15 button for speckit.sre-observability

Your own site · 80×15
<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.sre-observability"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.sre-observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 926 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00032 $0.00926
Opus 5 $0.00016 $0.00463
Sonnet 5 $0.00006 $0.00185
Haiku 4.5 $0.00003 $0.00093

Measured 11d ago against content hash f9c3755f7d7e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

speckit.sre-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 11d 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.

.agents/skills/speckit.sre-observability/SKILL.md · 62 lines

How it starts

The opening of the file, as written. The whole thing — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.

🎯 Mission

Design, configure, and enforce enterprise-grade Observability and Site Reliability Engineering (SRE) standards across services. Ensure system state is fully transparent through the Three Pillars (Logs, Metrics, Traces), actionable alerts, and battle-tested resilience patterns.

📥 Required Inputs

  • .agents/specs/[feature]/spec.md, plan.md, and tasks.md
  • Service architecture, topology, and SLA/SLO commitments
  • Infrastructure configs (docker-compose.yml, Kubernetes manifests, Helm charts)

📋 Protocol

1. Distributed Tracing & OpenTelemetry (OTel)

  • Trace Context Propagation: Propagate W3C TraceContext headers (traceparent, tracestate) across all HTTP, gRPC, and message queue boundaries.
  • Span Granularity: Instrument high-level operations: incoming HTTP request, external API calls, DB transactions, background jobs, and cache accesses.
  • Baggage & Correlation: Attach trace_id, span_id, service.name, and environment to all telemetry data.

2. Metrics Architecture (RED & USE Methods)

  • RED Method (Request-driven Services):
    • Rate: Requests per second (Counter).
    • Errors: Failed requests count partitioned by HTTP status code / error type (Counter).
    • Duration: Request latency distribution (Histogram with standardized buckets: 0.005s, 0.01s, 0.025s, 0.05s, 0.1s, 0.25s, 0.5s, 1s, 2.5s, 5s, 10s).
  • USE Method (Resources - CPU, RAM, Disk, DB Pools):
    • Utilization: Percent time busy.
    • Saturation: Queue length or waiting threads.
    • Errors: Device or connection error count.

3. Structured Logging Standard

  • Format: 100% Structured JSON logs emitted to stdout / stderr.
  • Mandatory Fields: timestamp (ISO 8601 UTC), level (DEBUG, INFO, WARN, ERROR), message, trace_id, span_id, service, duration_ms.
  • Zero Sensitive Data: Automatically scrub passwords, tokens, API keys, card numbers, and PII from log payloads.

4. Health Checks & Lifecycle Management

  • Liveness Probe (/livez): Returns 200 OK if the process is running. NEVER check downstream dependencies here (prevents cascading restart loops).
  • Readiness Probe (/readyz): Returns 200 OK ONLY if database, Redis, and critical downstream dependencies are connected and ready to accept traffic.
  • Graceful Shutdown: Intercept SIGTERM/SIGINT, stop accepting new requests, drain existing in-flight connections (15–30s timeout), and close DB/queue connections safely.

Read the full file on GitHub · 62 lines

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. 11d ago First seen · 62 lines · 32 tokens per session scan A f9c3755f7d7e

Subscribe to this mod's changes

speckit.sre-observability is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 15d ago), licensed MIT. It adds 32 tokens to every session and 926 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.