monitoring-observability

monitoring-observability is a skill for Claude Code, Codex from 0xranx/agentbrief. It costs 57 tokens per session (2,377 once invoked), scanned A, original, MIT.

A skill for setting up monitoring and observability, meaning the collection of information that shows whether software and infrastructure are working correctly.

In plain words
What is it for?
Use it to add health checks, metrics, logs, and alerts with tools such as Prometheus, Grafana, ELK, or Datadog.
Why use it?
It helps teams detect failures, measure performance, investigate incidents, and track service availability instead of relying only on user reports.

Skill for Claude CodeCodex

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

Good fit Use it to add health checks, metrics, logs, and alerts with tools such as Prometheus, Grafana, ELK, or Datadog.

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

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 monitoring-observability

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/0xranx/agentbrief/monitoring-observability"><img src="https://agentmods.dev/badge/skills/0xranx/agentbrief/monitoring-observability.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,377 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.00057 $0.02377
Opus 5.5 $0.00023 $0.00951
Sonnet 5.5 $0.00011 $0.00475
Haiku 4.5 $0.00006 $0.00238

Measured 1mo ago against content hash 193326801875, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

monitoring-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 1mo 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.

briefs/devops-sre/skills/monitoring-observability/SKILL.md · 395 lines

How it starts

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

Monitoring & Observability

When to use this skill

  • Before Production Deployment: Essential monitoring system setup
  • Performance Issues: Identify bottlenecks
  • Incident Response: Quick root cause identification
  • SLA Compliance: Track availability/response times

Instructions

Step 1: Metrics Collection (Prometheus)

Application Instrumentation (Node.js):

import express from 'express';
import promClient from 'prom-client';

const app = express();

// Default metrics (CPU, Memory, etc.)
promClient.collectDefaultMetrics();

// Custom metrics
const httpRequestDuration = new promClient.Histogram({
  name: 'http_request_duration_seconds',
  help: 'Duration of HTTP requests in seconds',
  labelNames: ['method', 'route', 'status_code']
});

const httpRequestTotal = new promClient.Counter({
  name: 'http_requests_total',
  help: 'Total number of HTTP requests',
  labelNames: ['method', 'route', 'status_code']
});

// Middleware to track requests
app.use((req, res, next) => {
  const start = Date.now();

  res.on('finish', () => {
    const duration = (Date.now() - start) / 1000;
    const labels = {
      method: req.method,
      route: req.route?.path || req.path,
      status_code: res.statusCode
    };

    httpRequestDuration.observe(labels, duration);
    httpRequestTotal.inc(labels);
  });

  next();
});

// Metrics endpoint
app.get('/metrics', async (req, res) => {
  res.set('Content-Type', promClient.register.contentType);
  res.end(await promClient.register.metrics());
});

app.listen(3000);

prometheus.yml:

global:
  scrape_interval: 15s
  evaluation_interval: 15s

scrape_configs:
  - job_name: 'my-app'
    static_configs:
      - targets: ['localhost:3000']
    metrics_path: '/metrics'

  - job_name: 'node-exporter'
    static_configs:
      - targets: ['localhost:9100']

alerting:
  alertmanagers:
    - static_configs:
        - targets: ['localhost:9093']

rule_files:
  - 'alert_rules.yml'

Read the full file on GitHub · 395 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. 1mo ago First seen · 395 lines · 57 tokens per session scan A 193326801875

Subscribe to this mod's changes

monitoring-observability is a skill published in the GitHub repository 0xranx/agentbrief (45 stars, last pushed 6mo ago), licensed MIT. It adds 57 tokens to every session and 2,377 once invoked, about $0.0002 per session on Opus 5.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-30.

Related

Other skills, from other repositories

multi-agent-design

A guide to deciding when several AI agents should work together and how they should share tasks, context, and files. It compares peer, manager-led, and decentralised arrangements and explains common coordination failures.

bojieli/ai-agent-book · 126 tokens

agent-state-bar

A design guide for an agent status bar: a short, automatically updated summary of progress, remaining tasks, tool counts, errors, and system state placed near the latest model input.

bojieli/ai-agent-book · 105 tokens

context-engineering

A guide to organizing the instructions and information an AI agent receives at each step. It covers system prompts, tool descriptions, conversation history, on-demand skills, and protections against unsafe outside content.

bojieli/ai-agent-book · 96 tokens

kv-cache-design

A guide to arranging an AI agent's conversation so previously processed text can be reused. A KV cache stores intermediate results for earlier tokens, while a prompt cache reuses a stable beginning across requests.

bojieli/ai-agent-book · 91 tokens

loop-engineering

A guide to building reliable loops for AI agents that plan, act, check their work, and continue until a task is truly complete. It includes independent verification and a proposer-reviewer pattern in which one agent's work is checked using outside evidence.

bojieli/ai-agent-book · 139 tokens

reward-design

A guide to defining the scores that an AI agent receives during trial-and-error training. It covers checks based on rules, human preferences, or another model, and distinguishes rewarding the final result from rewarding the steps taken.

bojieli/ai-agent-book · 131 tokens