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 skills/nahisaho/codegraphmcpserver/site-reliability-engineernpx skills add nahisaho/CodeGraphMCPServer --skill site-reliability-engineergit clone --depth 1 https://github.com/nahisaho/CodeGraphMCPServerWhat 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.00221 | $0.03775 |
| Opus 5 | $0.00111 | $0.01887 |
| Sonnet 5 | $0.00044 | $0.00755 |
| Haiku 4.5 | $0.00022 | $0.00378 |
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.
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
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 · 532 lines · 221 tokens per session scan A 350540ccbbaf
site-reliability-engineer is a skill published in the GitHub repository nahisaho/CodeGraphMCPServer (12 stars, last pushed 8mo ago), licensed MIT. It adds 221 tokens to every session and 3,775 once invoked, about $0.0011 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…