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 skills add MotWakorb/ai-agent-dev-team --skill sregit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/motwakorb/ai-agent-dev-team/sre)<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="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.1 | $0.00072 | $0.05703 |
| Opus 5 | $0.00036 | $0.02851 |
| Sonnet 5 | $0.00014 | $0.01141 |
| Haiku 4.5 | $0.00007 | $0.00570 |
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 8d 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 — 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
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.
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.
- 8d ago First seen · 405 lines · 72 tokens per session scan A 451ae9869e30
sre is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 25d ago), licensed MIT. It adds 72 tokens to every session and 5,703 once invoked, about $0.0004 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…