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/serenorg/seren/site-reliability-engineernpx skills add serenorg/seren --skill site-reliability-engineergit clone --depth 1 https://github.com/serenorg/serenWrote 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/skills/serenorg/seren/site-reliability-engineer)<a href="https://agentmods.dev/skills/serenorg/seren/site-reliability-engineer"><img src="https://agentmods.dev/badge/skills/serenorg/seren/site-reliability-engineer.svg" alt="Measured on agentmods" 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 | $0.00013 | $0.00249 |
| Opus 5 | $0.00006 | $0.00125 |
| Sonnet 5 | $0.00003 | $0.00050 |
| Haiku 4.5 | $0.00001 | $0.00025 |
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 4d 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
Run an evidence-first reliability workflow:
- Establish the affected service, time window, reported symptom, and current customer impact.
- Gather authorized service health, alert, deployment, code-change, incident-discussion, and runbook evidence.
- Normalize timestamps and build a concise event timeline.
- Assess blast radius across services, regions, organizations, and customer workflows without exposing private customer data.
- Rank likely causes by supporting evidence, contradictory evidence, confidence, and the next observation that would confirm or reject each hypothesis.
- Recommend reversible diagnostic steps, rollback criteria, escalation owners, and communication checkpoints.
- If a low-risk incident coordination update is warranted, show the exact proposed action and request operator approval.
- After approval, execute at most one permitted mutation with an idempotency key, verify the result, and stop. If approval is denied or unavailable, make no change.
- Finish with an incident triage brief that separates verified facts, hypotheses, unknowns, approved actions, and decisions needed.
If a required source is unavailable, mark it unknown rather than inferring its contents.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 21 lines · 13 tokens per session scan A 2d1ec54c1032
site-reliability-engineer is a skill published in the GitHub repository serenorg/seren (5 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 249 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-31.
Other skills, from other repositories
alloydb-basics
Manages clusters, instances, and backups for AlloyDB for PostgreSQL, and integrates with AlloyDB Model Context Protocol (MCP) tools for automated database operations. Use when creating, configuring, or administering AlloyDB databases. Do NOT use for general PostgreSQL instances (e.g. Cloud SQL) or other GCP databases.
bigquery-bigframes
Generates Python code using BigQuery DataFrames (BigFrames), the pandas/scikit-learn-style API over BigQuery. Use when writing BigFrames code or doing pandas-style dataframe/ML work against BigQuery (e.g. in a notebook). Don't use for SQL-first workflows or the google-cloud-bigquery client library — use…
cloud-databases-onboarding
Guides users through discovering their database requirements, recommends a Google Cloud database based on a recommendation matrix, and assists in database creation. Use when a user asks 'What database service should I use?', 'Help me pick a database', or when a user wants to create a new database on Google Cloud.…
cloud-sql-basics
This file generates or explains Cloud SQL resources. Use this file when the user asks to create a Cloud SQL instance or database for MySQL, PostgreSQL, or SQL Server. Cloud SQL manages third-party MySQL, PostgreSQL, and SQL Server instances as resources in Cloud SQL. For example, when Cloud SQL creates an open-source…
obsidian-bases
Create and edit Obsidian Bases (.base files) with views, filters, formulas, and summaries. Use when working with .base files, creating database-like views of notes, or when the user mentions Bases, table views, card views, filters, or formulas in Obsidian.
supabase
Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase/ssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies…