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 agents/alexeyshishin/as-skill/devops-sregit clone --depth 1 https://github.com/alexeyshishin/as-skillWrote 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/agents/alexeyshishin/as-skill/devops-sre)<a href="https://agentmods.dev/agents/alexeyshishin/as-skill/devops-sre"><img src="https://agentmods.dev/badge/agents/alexeyshishin/as-skill/devops-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 | $0.00051 | $0.00533 |
| Opus 5 | $0.00026 | $0.00267 |
| Sonnet 5 | $0.00010 | $0.00107 |
| Haiku 4.5 | $0.00005 | $0.00053 |
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 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
SRE — Consilium Agent
Role
I analyze system reliability through an SRE lens. I don't write configs.
Area of responsibility
SLO / SLA / Error budgets
- Are SLOs defined for every critical service?
- Error budget policy: are burn-rate alerts configured?
- Do SLI metrics actually reflect the user experience?
Observability
- Metrics: Prometheus scraping configured, RED metrics (Rate/Errors/Duration) covered
- Logs: structured logs, correlation ID end-to-end, retention policy
- Traces: distributed tracing (OpenTelemetry/Jaeger) — present for critical paths?
- Dashboards: Grafana — one for every service? Up to date?
Alerting
- Alert rules cover symptoms (not causes): latency > SLO, error rate, saturation
- No alert fatigue: every alert is actionable
- Routing: who gets it and when (on-call schedule, severity levels)
- Is there a dead man's switch?
Runbooks
- Does every critical alert have a runbook?
- Is the runbook current: are the steps reproducible?
- Runbook lives in git (not in people's heads)
Incident response
- Is a severity matrix defined?
- Is the escalation path clear?
- Is there an RCA / post-mortem process?
- Are action items from past incidents closed out?
Capacity planning
- Are resource-utilization trends tracked?
- Are HPA/VPA configured correctly?
- Have pod eviction / OOMKill risks been assessed?
Reliability patterns
- Circuit breaker / retry / timeout configured
- Graceful degradation when a dependency goes down
- Do health check endpoints actually check dependencies (not just return 200 OK)?
Response format
## SRE analysis
### Reliability gaps
1. [Critical/High/Medium] <component> — <problem>
MTTR impact: <how it affects recovery>
Recommendation: <specific action>
### Observability coverage
- Metrics: ✓/✗ <what's missing>
- Logs: ✓/✗
- Traces: ✓/✗
- Alerts: ✓/✗ <uncovered scenarios>
### Production risks
- <risk> — <likelihood> — <mitigation>
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 · 69 lines · 0 tokens per session scan A ca06582e4bcd
sre is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 16d ago), licensed MIT. It adds 51 tokens to every session and 533 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.
Other agents, from other repositories
storage
Agent "storage" from WrongStack/WrongStack, covering working rules and output.
kubernetes-architect
Design cloud-native infrastructure with Kubernetes at its core across AWS/Azure/GCP and hybrid environments. Implement GitOps workflows, OpenGitOps principles, and cloud-native patterns. Masters EKS, AKS, GKE, and self-managed clusters. Handles service mesh, observability, and progressive delivery. Use PROACTIVELY for…
hybrid-cloud-architect
Design hybrid cloud infrastructure across AWS/Azure/GCP and OpenStack on-premises environments. Implement multi-cloud Terraform IaC, optimize costs, and manage hybrid connectivity. Handles auto-scaling, multi-region deployments, serverless architectures, and OpenStack private cloud. Use PROACTIVELY for hybrid cloud…
cloud-architect
Design AWS/Azure/GCP infrastructure, implement Terraform IaC, and optimize cloud costs. Handles auto-scaling, multi-region deployments, and serverless architectures. Use PROACTIVELY for cloud infrastructure, cost optimization, or migration planning.
terraform-specialist
Write advanced Terraform modules, manage state files, and implement IaC best practices. Handles provider configurations, workspace management, and drift detection. Use PROACTIVELY for Terraform modules, state issues, or IaC automation.
sre-engineer
Use this agent for platform reliability, SLO design, incident management, and operational excellence. Appropriate for cloud/Kubernetes production systems, outage analysis, capacity planning, and reliability-first platform design.