agentmods.dev

sre

sre is a skill for Claude Code from MotWakorb/ai-agent-dev-team. It costs 72 tokens per session (5,703 once invoked), scanned A, original, MIT.

A guide for keeping software services running reliably, including monitoring, service targets, incident response, capacity, and on-call preparation.

In plain words
What is it for?
Use it to plan observability, define SLOs and SLAs, prepare incident response, manage capacity, check restart and backup behavior, and control monitoring costs.
Why use it?
It replaces guesses about reliability with appropriate evidence and practices for the system's operating level.

Skill for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: model in frontmatter.

not rated 2repo 2mo ago A scan 72 tokens original MIT

Good fit Use it to plan observability, define SLOs and SLAs, prepare incident response, manage capacity, check restart and backup behavior, and control monitoring costs.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/motwakorb/ai-agent-dev-team/sre
View source ↗ MotWakorb/ai-agent-dev-team
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.

Any agent
npx skills add MotWakorb/ai-agent-dev-team --skill sre
Clone the repo
git clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-team

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.

agentmods badge for sre

README.md
[![agentmods](https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/sre/github.svg)](https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/sre)
Your own site
<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/sre"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/sre/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.

agentmods 80×15 button for sre

Your own site · 80×15
<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/sre"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/sre.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,703 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.05703
Opus 5.5 $0.00029 $0.02281
Sonnet 5.5 $0.00014 $0.01141
Haiku 4.5 $0.00007 $0.00570

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

Security

Grade A, and why

sre 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.

sre/SKILL.md · 405 lines

How it starts

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

Site Reliability Engineer

Follow the shared Engineering Discipline principles. Evidence over intuition. When someone says "it's reliable," ask for the appropriate evidence — at startup/enterprise tiers that's the SLO and dashboard; at home-lab tier that's "it auto-restarts and you have backups." Feelings about reliability are not reliability.

Calibrate to deployment tier. Read ../_shared/deployment-tier.md — including the SRE calibration table — and the project's COMPONENTS.md. The "Hard Rules" below describe maximum rigor (enterprise tier); apply the per-tier baseline, and frame higher-tier practices as "at a higher tier I would also recommend X," not as findings.

You are a senior SRE who owns the operational reality of everything the team builds. The architect designs for operational excellence; you verify it and make it real. The engineer deploys the code; you make sure it stays running. At enterprise tier you are the person who gets paged at 3 AM. At home-lab tier you are the person who makes sure the operator gets an email when something dies and can restore from backup.

Philosophy

Reliability Is a Feature

Users don't care about your architecture, your test coverage, or your deployment pipeline. They care that the product works when they need it. Reliability is the feature that makes all other features possible.

SLOs Drive Everything

Without defined SLOs, there is no objective measure of reliability. "It feels reliable" is not engineering — it's hope:

  • SLI (Service Level Indicator): The metric you measure (latency p99, error rate, availability)
  • SLO (Service Level Objective): The target you commit to (99.9% availability, p99 latency < 200ms)
  • SLA (Service Level Agreement): The contractual commitment to customers (with consequences for missing it)
  • Error Budget: The inverse of SLO — if your SLO is 99.9%, you have 0.1% error budget (43 minutes/month of downtime). When the budget is spent, reliability work takes priority over feature work

Read the full file on GitHub · 405 lines

Files

What ships with it

1 file 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.

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. 2mo ago First seen · 405 lines · 72 tokens per session scan A 451ae9869e30

Subscribe to this mod's changes

sre is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 5,703 once invoked, about $0.0003 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-31.

DevOps and cloud
Related

sre compared with skills from other repositories

sre next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
sreMotWakorb/ai-agent-dev-teamSkill22mo agoMITA72Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
playwright-climicrosoft/playwrightSkill99ktodayApache-2.0A19Claude Code
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79ktodayMITA200Claude Code, Codex
systematic-debuggingobra/superpowersSkill314k3d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143kyesterdayMITA95Claude Code
next-partial-prefetching-adoptionvercel/next.jsSkill143kyesterdayMITA103Claude Code