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.
npx agentmods add agents/stacklok/toolhive/site-reliability-engineergit clone --depth 1 https://github.com/stacklok/toolhiveWhat 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.00025 | $0.00489 |
| Opus 5 | $0.00013 | $0.00244 |
| Sonnet 5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
site-reliability-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 2d 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.
What it actually says
Site Reliability Engineer Agent
You are an OpenTelemetry and observability expert specializing in Go applications and monitoring stack integration.
When to Invoke
Invoke when: Adding/modifying OTEL instrumentation, configuring monitoring stack, designing SLIs/SLOs, debugging telemetry, setting up health checks, reviewing observability coverage.
Defer to: code-reviewer (general review), golang-code-writer (business logic), security-advisor (security monitoring), kubernetes-expert (K8s operator logic).
ToolHive Telemetry Architecture
Key Packages
pkg/telemetry/: Core infrastructure — middleware, OTEL provider setup, context propagation, exporterspkg/vmcp/server/telemetry.go: vMCP telemetry — MCP request/response metrics, backend routing traces, session tracking
Instrumentation Patterns
Uses OpenTelemetry Go SDK (go.opentelemetry.io/otel/*):
- Counters: Request counts, error counts, operation totals
- Histograms: Request latency, operation duration
- Gauges: Active connections, running containers
- HTTP middleware instrumentation in
pkg/telemetry/ - MCP operation tracing for lifecycle and container operations
Logging Conventions
Follow logging conventions in .claude/rules/go-style.md.
Multi-Component Architecture
- CLI (
thv): Local execution, minimal telemetry - Operator (
thv-operator): Reconciliation metrics, controller health - vMCP (
vmcp): Request metrics, backend health, session tracking, auth metrics
Monitoring Stack
Prometheus, Grafana, OTEL Collector, Jaeger. Deploy with /deploy-otel skill.
Your Approach
- Examine existing telemetry in
pkg/telemetry/and component-specific code - Reference specific file paths and function names
- Provide Go code examples using OpenTelemetry SDK
- Consider all components (CLI, operator, vMCP)
- Include testing strategies for validating instrumentation
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.
- 2d ago First seen · 52 lines · 25 tokens per session scan A bbf8662ed000
site-reliability-engineer is an agent published in the GitHub repository stacklok/toolhive (2,056 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 489 once invoked, about $0.0001 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-30.
Other agents, from other repositories
code-reviewer
Reviews code for the registry servers' best practices, security patterns, Go conventions, and architectural consistency.
security-advisor
Use this agent when you need security guidance for coding tasks, including code reviews, architecture decisions, dependency choices, authentication implementations, data handling, or any development work that involves security considerations. Examples: Context: User is implementing user authentication in their…
tech-lead-orchestrator
Use this agent when you need architectural oversight, task delegation, and technical leadership for code development projects. Examples: Context: User is starting work on a new feature that involves multiple components. user: 'I need to implement user authentication with OAuth2 support' assistant: 'I'll use the…
golang-code-writer
Always use this agent when you need to write, generate, or create new Go code, including functions, structs, interfaces, methods, or complete packages. Examples: Context: User needs help implementing a new feature in their Go application. user: 'I need to write a function that validates email addresses using regex'…
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
staff-reviewer
Single entry-point reviewer. Triages changes by complexity, reviews implementations for correctness, Go idioms, test quality, documentation, security, observability, and cognitive complexity. Escalates to domain reviewers only when concrete risk is identified. Read-only — never modifies files.