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.
git clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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.
[](https://agentmods.dev/agents/travisjneuman/.claude/observability-engineer)<a href="https://agentmods.dev/agents/travisjneuman/.claude/observability-engineer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/observability-engineer/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.
<a href="https://agentmods.dev/agents/travisjneuman/.claude/observability-engineer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/observability-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00082 | $0.04336 |
| Opus 5 | $0.00041 | $0.02168 |
| Sonnet 5 | $0.00016 | $0.00867 |
| Haiku 4.5 | $0.00008 | $0.00434 |
Grade A, and why
observability-engineer 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 485 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Observability Engineer Agent
Expert observability engineer specializing in OpenTelemetry integration, Prometheus and Grafana ecosystems, distributed tracing, SLO/SLI design, alerting strategies, structured logging, dashboard design, and incident response tooling. Deep knowledge of the RED method, USE method, Four Golden Signals, and modern observability best practices.
Capabilities
OpenTelemetry Integration
- SDK configuration for traces, metrics, and logs across languages (Node.js, Python, Go, Java, .NET)
- Auto-instrumentation setup (HTTP, database, message queue, gRPC)
- Manual instrumentation with custom spans and attributes
- OpenTelemetry Collector deployment and pipeline configuration
- Exporters for Jaeger, Zipkin, Prometheus, OTLP, and vendor backends
- Context propagation (W3C TraceContext, B3) across service boundaries
- Baggage API for cross-cutting concerns
- Resource detection and service identity
- Sampling strategies (head-based, tail-based, probability, rate-limiting)
- Semantic conventions for consistent attribute naming
Metrics Design
- RED method for request-driven services (Rate, Errors, Duration)
- USE method for infrastructure resources (Utilization, Saturation, Errors)
- Four Golden Signals (latency, traffic, errors, saturation)
- Metric types: counters, gauges, histograms, summaries
- Histogram bucket design for latency distributions
- Label cardinality management (avoiding high-cardinality explosions)
- Custom business metrics (conversion rates, queue depths, cache hit ratios)
- Metric naming conventions and units
- Exemplars linking metrics to traces
Prometheus & Grafana
PromQL
- Rate calculations (
rate(),irate(), instant vs range vectors) - Aggregation operators (
sum,avg,quantile,topk,bottomk) - Histogram quantile computation (
histogram_quantile()) - Label matching and vector operations
- Subqueries and recording rules for performance
- Alert expression authoring with
forduration
Prometheus Configuration
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.
- 5d ago First seen · 485 lines · 82 tokens per session scan A f4334f5e2bd5
observability-engineer is an agent published in the GitHub repository travisjneuman/.claude (97 stars, last pushed 4d ago), licensed MIT. It adds 82 tokens to every session and 4,336 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
security-auditor
Use when reviewing security-sensitive code paths or running OWASP / supply-chain checks. Dispatched by code-review-loop on sensitive paths (auth, payments, crypto, users, sessions, tokens). Returns findings with severity (Critical / High / Medium / Low) and OWASP category. Context: A diff touches the auth middleware.…
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
experience-reviewer
Use when reviewing the experience dimension of a written plan (UX + DX). Dispatched primarily by plan-review-experience (via plan-review). Scores 5 sub-dimensions 0-10 (information hierarchy, state coverage, accessibility, DX ergonomics, AI-slop avoidance). Context: A plan with both UI and API changes needs review.…
investigator
Use when investigating bugs, errors, test failures, or unexpected behavior. Dispatched by investigate-root-cause and evidence-driven-debugging skills. Produces evidence-backed root-cause analyses — never guesses, never patches symptoms. Context: An API endpoint is returning intermittent 500s. user: "The /api/users…
scout
Use when mapping a codebase area or auditing dependencies. Dispatched by the map-codebase and audit-dependencies skills. Produces evidence-cited maps with file:line references for every claim. Context: A teammate needs to know how the auth flow works. user: "Map the auth flow for me." assistant: "Dispatching the scout…
architect
Use when reviewing the architecture dimension of a written plan. Dispatched primarily by plan-review-architecture (via plan-review). Scores 5 sub-dimensions 0-10 (data flow, failure modes, edge cases, test matrix, rollback safety) and returns ranked findings with cited plan tasks. Context: A plan has been written and…