What is oma-observability?

An observability design and routing assistant for telemetry such as metrics, logs, traces, profiles, application monitoring, and user-experience monitoring.

Use it to design OpenTelemetry pipelines, trace requests across service boundaries, tune telemetry transport, define observability as code, select monitoring tools, and investigate incidents.

It helps choose and connect the right monitoring approach across services, infrastructure, vendors, and incident investigations.

oma-observability — Skill for Claude Code and Codex by first-fluke: An observability design and routing assistant for telemetry such…

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 skills/first-fluke/fullstack-starter/oma-observability

Any agent

npx skills add first-fluke/fullstack-starter --skill oma-observability

Clone the repo

git clone --depth 1 https://github.com/first-fluke/fullstack-starter

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-observability.svg)](https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-observability)

Your own site

<a href="https://agentmods.dev/skills/first-fluke/fullstack-starter/oma-observability"><img src="https://agentmods.dev/badge/skills/first-fluke/fullstack-starter/oma-observability.svg" alt="Measured on agentmods" height="20"></a>

Per session 78 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,477 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod 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.

Model	Per session	Once invoked
Fable 5	$0.00078	$0.04477
Opus 5	$0.00039	$0.02239
Sonnet 5	$0.00016	$0.00895
Haiku 4.5	$0.00008	$0.00448

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

Security

Grade A, and why

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

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.

Origin

This is a copy

100% identical to oma-observability — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.agents/skills/oma-observability/SKILL.md · 325 lines

How it starts

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

Observability Agent - Intent-based Router

Scheduling

Goal

Route, design, tune, and review observability work across MELT+P signals, layers, boundaries, vendor categories, transport choices, meta-observability, and incident forensics.

Intent signature

User asks for observability, telemetry, OTel, metrics, logs, traces, profiles, SLOs, RUM, APM, incident forensics, trace propagation, transport tuning, or observability-as-code.
User needs vendor/category routing or observability architecture instead of a single vendor's already-covered setup.

When to use

Setting up an observability pipeline (OTel SDK + Collector + vendor backend)
Designing traceability across service and domain boundaries (W3C propagators, baggage, multi-tenant, multi-cloud)
Tuning transport layer (UDP/MTU, OTLP gRPC vs HTTP, Collector DaemonSet vs sidecar topology)
Running incident forensics (6-dimension localization: code / service / layer / host / region / infra)
Selecting a vendor category (OSS full-stack vs commercial SaaS vs high-cardinality specialist vs profiling specialist)
Implementing observability-as-code (Grafana Jsonnet dashboards, PrometheusRule CRD, OpenSLO YAML, SLO burn-rate alerts)
Meta-observability (pipeline self-health, clock skew detection, cardinality guardrails, retention matrix)
Covering the MELT+P signal set: metrics, logs, traces, profiles (OTEP 0239), cost (OpenCost), audit (SOC2/ISO), privacy (GDPR/PIPA)
Migrating off deprecated tools (Fluentd → Fluent Bit or OTel Collector, per CNCF 2025-10 guide)

When NOT to use

LLM ops (prompt versioning, evals, gen_ai span deep dive); use Langfuse, Arize Phoenix, LangSmith, or Braintrust directly
Data pipeline lineage: use OpenLineage + Marquez, dbt test, or Airflow lineage backends
IoT / hardware / datacenter physical-layer telemetry (IPMI, BMC, SNMP); use vendor DCIM tooling (Nlyte, Sunbird, Device42)
Chaos engineering orchestration: use Chaos Mesh, Litmus, Gremlin, or ChaosToolkit (this skill consumes their telemetry; it does not orchestrate chaos)
GPU / TPU infrastructure observability: use NVIDIA DCGM Exporter + Prometheus
Software supply chain (SBOM, attestation): use sigstore (cosign / rekor), in-toto framework, SLSA level attestations
Incident response workflow (on-call rotation, paging, escalation); use PagerDuty, OpsGenie, or Grafana OnCall
Single-vendor setup already fully covered by that vendor's own published skill; invoke the vendor skill directly

Read the full file on GitHub · 325 lines

Files

What ships with it

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

yesterday First seen · 325 lines · 78 tokens per session scan A c40a1e367611

Subscribe to this mod's changes

oma-observability is a skill published in the GitHub repository first-fluke/fullstack-starter (222 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 4,477 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to oma-observability, differing in 0 lines, and is treated as a copy.

Analytics and metrics DevOps and cloud fastapi flutter gcp mise monorepo nextjs

background-task

Add or modify work that runs outside the request/response cycle — emails, document ingestion, webhooks, cleanups, scheduled jobs. Use when something is slow or fire-and-forget, or when adding a periodic/cron task. This project's queue is {{ cookiecutter.backgroundtasks }}.

vstorm-co/full-stack-ai-agent-template · 62 tokens

frontend-feature

Build a new page, view, or data-driven feature in the Next.js frontend. Use when adding a route under the dashboard/marketing area, wiring UI to a backend endpoint, adding client state, or creating a localized page. Covers App Router, data fetching, Zustand stores, and i18n.

vstorm-co/full-stack-ai-agent-template · 64 tokens

pytest-suite

Write or extend the backend test suite following this project's conventions. Use when adding tests for a new service/route/repository, when coverage is missing, or when asked to test a feature. Knows the mocked-session + httpx AsyncClient setup so tests run with no database.

vstorm-co/full-stack-ai-agent-template · 59 tokens

rag-knowledge

Work with the RAG knowledge base — ingest documents, run semantic search, manage collections, or add a sync source/connector (Google Drive, S3). Use when populating or debugging the knowledge base, tuning retrieval, or adding a new document source. This project uses {{ cookiecutter.vectorstore }} + {{…

vstorm-co/full-stack-ai-agent-template · 76 tokens

alembic-migration

Create, review, and apply database schema changes with Alembic. Use whenever a SQLAlchemy model is added or changed, a column/index/constraint needs to change, or a data backfill is required — anything that alters the PostgreSQL schema.

vstorm-co/full-stack-ai-agent-template · 56 tokens

billing-stripe

Work with Stripe billing — subscriptions, plans/prices, the Customer Portal, credits, usage metering, invoices, and webhook events. Use when changing plans, handling a new Stripe webhook, debugging a payment/subscription flow, or touching credit balances and usage.