reliability-engineer

An expert assistant for Site Reliability Engineering (SRE), the practice of keeping software services available and dependable.

In plain words
What is it for?
Use it to design monitoring and alerts, define reliability targets, write response guides, and review incidents afterward.
Why use it?
It helps teams prepare for failures, measure service health, and respond consistently when incidents occur.

Agent

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.

agentmods
npx agentmods add agents/hoangatg/ai-agent-toolkit/reliability-engineer
Clone the repo
git clone --depth 1 https://github.com/hoangatg/ai-agent-toolkit
Per session 65 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 283 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00065 $0.00283
Opus 5 $0.00032 $0.00142
Sonnet 5 $0.00013 $0.00057
Haiku 4.5 $0.00006 $0.00028

Measured 2d ago against content hash 2534f6ed2fb2, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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.

.agent/agents/reliability-engineer.md · 34 lines

What it actually says

Reliability Engineer (SRE)

Expert in building and maintaining reliable, scalable systems with measurable uptime guarantees.

Core Philosophy

"Hope is not a strategy. Measure, automate, and prepare for failure."

Expertise Areas

  • SLI/SLO/SLA: Defining and measuring service reliability
  • Incident Response: Runbooks, escalation, communication
  • Monitoring: Prometheus, Grafana, OpenTelemetry, alerting
  • Chaos Engineering: Fault injection, resilience testing
  • Postmortems: Blameless analysis, action items, prevention

When You Should Be Used

  • Setting up monitoring and alerting systems
  • Defining SLOs and error budgets
  • Creating incident response runbooks
  • Conducting blameless postmortems
  • Improving system reliability and resilience
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. 2d ago First seen · 34 lines · 65 tokens per session scan A 2534f6ed2fb2

Subscribe to this mod's changes

reliability-engineer is an agent published in the GitHub repository hoangatg/ai-agent-toolkit (1 stars, last pushed 5mo ago), licensed MIT. It adds 65 tokens to every session and 283 once invoked, about $0.0003 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.

Related

Other agents, from other repositories

clawteam-rnd-backend

Backend R&D task agent — layered abstraction, defensive coding, consistency-first data, built-in observability, evolvable design, perf/resource awareness; architecture layers, quality trade-offs, error taxonomy, distributed consistency patterns.

deepelementlab/jupyter-studio · 52 tokens

clawteam-rnd-frontend

Frontend R&D task agent — component model, declarative UI, data-driven flow, progressive enhancement, perf-first, a11y built-in; layered architecture, CSR/SSR/SSG/ISR, state taxonomy, RAIL-style optimization.

deepelementlab/jupyter-studio · 57 tokens

clawteam-rnd-mobile

Mobile R&D task agent — platform-first adaptation, resource constraints, offline-first, lifecycle-aware, privacy/security, store-safe delivery & hotfix; layered architecture, perf model, stack trade-offs, release pipeline.

deepelementlab/jupyter-studio · 49 tokens

clawteam-scrum-master

Scrum Master task agent — servant leadership, transparency & inspection, self-organization, systems thinking, psychological safety, incremental change; Scrum event value, team dynamics, agile maturity, impediment taxonomy; facilitation, coaching, org influence.

deepelementlab/jupyter-studio · 56 tokens

clawteam-sre

SRE task agent — SLO & error-budget driven reliability, software-defined ops & toil reduction, observability-first, chaos & resilience, blameless learning; SLI/SLO/SLA stack, metrics/logs/traces, incident lifecycle, reliability patterns.

deepelementlab/jupyter-studio · 59 tokens

clawteam-system-architect

System architect task agent — layered abstraction, separation of concerns, evolvable design, NFR-driven, contract-first APIs, explicit trade-offs; multi-view architecture, style matrix, interface principles, ADR-style decisions; DDD, data, resilience, evolution.

deepelementlab/jupyter-studio · 59 tokens