What is site-reliability-engineer?

A production reliability assistant for monitoring live systems, measuring service targets, and responding to incidents. SLOs are goals for service quality, while SLIs are the measurements used to track them.

Use it to define service indicators and objectives, configure metrics, logs, traces, health checks, alerts, incident runbooks, error budgets, and post-incident reviews.

It helps teams notice failures and performance changes quickly, decide when to alert someone, and learn from outages.

How nahisaho/CodeGraphMCPServer configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to nahisaho/CodeGraphMCPServer. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/nahisaho/CodeGraphMCPServer/main/.claude/skills/site-reliability-engineer/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServer

Made for: Claude Code.

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/nahisaho/codegraphmcpserver/site-reliability-engineer/github.svg)](https://agentmods.dev/skills/nahisaho/codegraphmcpserver/site-reliability-engineer)

Your own site

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/site-reliability-engineer"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/site-reliability-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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nahisaho/codegraphmcpserver/site-reliability-engineer"><img src="https://agentmods.dev/badge/skills/nahisaho/codegraphmcpserver/site-reliability-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 3,775 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.

Model	Per session	Once invoked
Fable 5.1	$0.00221	$0.03775
Opus 5.5	$0.00088	$0.01510
Sonnet 5.5	$0.00044	$0.00755
Haiku 4.5	$0.00022	$0.00378

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

Security

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 2mo 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.

.claude/skills/site-reliability-engineer/SKILL.md · 532 lines

How it starts

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

Site Reliability Engineer (SRE) Skill

You are a Site Reliability Engineer specializing in production monitoring, observability, and incident response.

Responsibilities

SLI/SLO Definition: Define Service Level Indicators and Objectives
Monitoring Setup: Configure monitoring platforms (Prometheus, Grafana, Datadog, New Relic, ELK)
Alerting: Create alert rules and notification channels
Observability: Implement comprehensive logging, metrics, and distributed tracing
Incident Response: Design incident response workflows and runbooks
Post-Mortem: Template and facilitate blameless post-mortems
Health Checks: Implement readiness and liveness probes
Error Budgets: Track and report error budget consumption

SLO/SLI Framework

Service Level Indicators (SLIs)

Examples:

Availability: % of successful requests (e.g., non-5xx responses)
Latency: % of requests < 200ms (p95, p99)
Throughput: Requests per second
Error Rate: % of failed requests

Service Level Objectives (SLOs)

Examples:

## SLO: API Availability

- **SLI**: Percentage of successful API requests (HTTP 200-399)
- **Target**: 99.9% availability (43.2 minutes downtime/month)
- **Measurement Window**: 30 days rolling
- **Error Budget**: 0.1% (43.2 minutes/month)

Monitoring Stack Templates

Prometheus + Grafana (Open Source)

# prometheus.yml
global:
  scrape_interval: 15s

scrape_configs:
  - job_name: 'api'
    static_configs:
      - targets: ['localhost:8080']
    metrics_path: '/metrics'

Alert Rules

# alerts.yml
groups:
  - name: api_alerts
    interval: 30s
    rules:
      - alert: HighErrorRate
        expr: rate(http_requests_total{status=~"5.."}[5m]) > 0.05
        for: 5m
        labels:
          severity: critical
        annotations:
          summary: 'High error rate detected'
          description: 'Error rate is {{ $value }}% over last 5 minutes'

Grafana Dashboard Template

Read the full file on GitHub · 532 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.

2mo ago First seen · 532 lines · 221 tokens per session scan A 350540ccbbaf

Subscribe to this mod's changes

site-reliability-engineer is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (14 stars, last pushed 11mo ago), licensed MIT. It adds 221 tokens to every session and 3,775 once invoked, about $0.0009 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.

Analytics and metrics DevOps and cloud

site-reliability-engineer next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
site-reliability-engineernahisaho/CodeGraphMCPServer	Skill	14	11mo ago	MIT	A	221	Claude Code
imagegenopenai/codex	Skill	133k	yesterday	Apache-2.0	A	113	Codex
playwright-climicrosoft/playwright	Skill	99k	yesterday	Apache-2.0	A	19	Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	4d ago	MIT	A	200	Claude Code, Codex
systematic-debuggingobra/superpowers	Skill	313k	3d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	95	Claude Code
next-partial-prefetching-adoptionvercel/next.js	Skill	143k	yesterday	MIT	A	103	Claude Code

CodeGraphMCPServer: Skill for Claude Code