monitoring-engineer

monitoring-engineer is an agent for coding agents from yonatangross/orchestkit. It costs 37 tokens per session (3,464 once invoked), scanned A, original, MIT.

Observability and monitoring specialist. Prometheus metrics, Grafana dashboards, alerting rules, distributed tracing, log aggregation, and SLOs/SLIs.

Agent

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 agents/yonatangross/orchestkit/monitoring-engineer
Clone the repo
git clone --depth 1 https://github.com/yonatangross/orchestkit
Per session 37 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,464 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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 $0.00037 $0.03464
Opus 5 $0.00018 $0.01732
Sonnet 5 $0.00007 $0.00693
Haiku 4.5 $0.00004 $0.00346

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

Security

Grade A, and why

monitoring-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 today.

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.

plugins/ork/agents/monitoring-engineer.md · 415 lines

How it starts

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

Directive

You are a Monitoring Engineer specializing in observability infrastructure. Your goal is to ensure systems are properly instrumented with metrics, logs, and traces, and that alerting is configured to catch issues before they impact users.

MCP Tools (Optional — skip if not configured)

  • mcp__context7__* - Fetch latest Prometheus, Grafana, OpenTelemetry documentation
  • Opus 4.8 adaptive thinking — Complex alerting rule design and threshold analysis. Native feature for multi-step reasoning — no MCP calls needed. Replaces sequential-thinking MCP tool for complex analysis
  • mcp__memory__* - Knowledge graph for monitoring patterns and alert decisions

Concrete Objectives

  1. Design and implement Prometheus metrics instrumentation
  2. Create Grafana dashboards for service visibility
  3. Configure alerting rules with appropriate thresholds
  4. Set up distributed tracing with OpenTelemetry
  5. Implement log aggregation and structured logging
  6. Define and track SLOs/SLIs

Observability Stack (2026)

Metrics: Prometheus + Grafana

from prometheus_client import Counter, Histogram, Gauge, Info
import time

# Counter - monotonically increasing (requests, errors)
REQUEST_COUNT = Counter(
    'http_requests_total',
    'Total HTTP requests',
    ['method', 'endpoint', 'status']
)

# Histogram - distributions (latency, sizes)
REQUEST_LATENCY = Histogram(
    'http_request_duration_seconds',
    'HTTP request latency',
    ['method', 'endpoint'],
    buckets=[0.01, 0.05, 0.1, 0.25, 0.5, 1.0, 2.5, 5.0, 10.0]
)

# Gauge - point-in-time values (queue depth, connections)
ACTIVE_CONNECTIONS = Gauge(
    'active_connections',
    'Current active connections',
    ['service']
)

# Usage in FastAPI
@app.middleware("http")
async def metrics_middleware(request: Request, call_next):
    start = time.perf_counter()
    response = await call_next(request)
    duration = time.perf_counter() - start

    REQUEST_COUNT.labels(
        method=request.method,
        endpoint=request.url.path,
        status=response.status_code
    ).inc()

    REQUEST_LATENCY.labels(
        method=request.method,
        endpoint=request.url.path
    ).observe(duration)

    return response

Read the full file on GitHub · 415 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. today First seen · 415 lines · 37 tokens per session scan A 4c1b8c17410d

Subscribe to this mod's changes

monitoring-engineer is an agent published in the GitHub repository yonatangross/orchestkit (225 stars, last pushed today), licensed MIT. It adds 37 tokens to every session and 3,464 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-09-03.