observability-setup

observability-setup is a skill for Claude Code, Codex from nik-kale/sre-skills. It costs 41 tokens per session (2,327 once invoked), scanned A, original, MIT.

A guide to adding application monitoring through metrics, logs, and traces. Metrics summarize what is happening, logs record detailed events, and traces show how a request moves through a system.

In plain words
What is it for?
Instrumenting services, building dashboards, configuring alerts, adding structured logs, and setting up distributed tracing.
Why use it?
It helps teams detect failures, understand slow or broken requests, monitor resources, and set useful alerts and service targets.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Instrumenting services, building dashboards, configuring alerts, adding structured logs, and setting up distributed tracing.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nik-kale/sre-skills/observability-setup
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 nik-kale/sre-skills --skill observability-setup
Clone the repo
git clone --depth 1 https://github.com/nik-kale/sre-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 observability-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/nik-kale/sre-skills/observability-setup.svg)](https://agentmods.dev/skills/nik-kale/sre-skills/observability-setup)
Your own site
<a href="https://agentmods.dev/skills/nik-kale/sre-skills/observability-setup"><img src="https://agentmods.dev/badge/skills/nik-kale/sre-skills/observability-setup.svg" alt="Measured on agentmods" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,327 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.00041 $0.02327
Opus 5 $0.00020 $0.01163
Sonnet 5 $0.00008 $0.00465
Haiku 4.5 $0.00004 $0.00233

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

Security

Grade A, and why

observability-setup 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.

skills/observability-setup/SKILL.md · 414 lines

How it starts

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

Observability Setup

Comprehensive guide to implementing the three pillars of observability.

When to Use This Skill

  • Setting up monitoring for a new service
  • Adding metrics instrumentation
  • Implementing structured logging
  • Setting up distributed tracing
  • Designing dashboards
  • Configuring alerts

The Three Pillars

Pillar What It Answers Tools
Metrics What is happening? (aggregated) Prometheus, Datadog, CloudWatch
Logs What happened? (detailed) ELK, Loki, CloudWatch Logs
Traces How did it happen? (flow) Jaeger, Zipkin, X-Ray

Metrics

Essential Metrics (Minimum Viable Observability)

Every service needs these metrics:

RED Method (Request-driven services)
Rate:    requests_total (counter)
Errors:  requests_failed_total (counter)
Duration: request_duration_seconds (histogram)
USE Method (Resources)
Utilization: resource_usage_percent (gauge)
Saturation:  queue_depth (gauge)
Errors:      resource_errors_total (counter)

Metric Types

Type Use For Example
Counter Cumulative values (only increase) requests_total, errors_total
Gauge Values that go up and down connections_active, queue_size
Histogram Distribution of values request_duration_seconds
Summary Pre-calculated percentiles response_time (p50, p99)

Prometheus Instrumentation

Python:

from prometheus_client import Counter, Histogram, start_http_server

# Define metrics
REQUEST_COUNT = Counter(
    'http_requests_total',
    'Total HTTP requests',
    ['method', 'endpoint', 'status']
)

REQUEST_LATENCY = Histogram(
    'http_request_duration_seconds',
    'HTTP request latency',
    ['method', 'endpoint'],
    buckets=[.005, .01, .025, .05, .1, .25, .5, 1, 2.5, 5, 10]
)

# Use in request handler
@app.route('/api/users')
def get_users():
    with REQUEST_LATENCY.labels(method='GET', endpoint='/api/users').time():
        result = fetch_users()
        REQUEST_COUNT.labels(method='GET', endpoint='/api/users', status='200').inc()
        return result

Read the full file on GitHub · 414 lines

Files

What ships with it

2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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. 8d ago First seen · 414 lines · 41 tokens per session scan A 298ca8f98112

Subscribe to this mod's changes

observability-setup is a skill published in the GitHub repository nik-kale/sre-skills (11 stars, last pushed 7mo ago), licensed MIT. It adds 41 tokens to every session and 2,327 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens