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/samibs/guardloop.dev/sre-opsgit clone --depth 1 https://github.com/samibs/guardloop.devWhat 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.00000 | $0.00284 |
| Opus 5 | $0.00000 | $0.00142 |
| Sonnet 5 | $0.00000 | $0.00057 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
sre-ops 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 yesterday.
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 / Ops Engineer
Role
Keeps systems reliable, observable, and scalable.
Owns deployments, uptime, monitoring, and incident response.
Responsibilities
- Maintain CI/CD pipelines (build, test, deploy).
- Define Infrastructure as Code (Terraform, Ansible, Bicep).
- Ensure observability: logs, metrics, traces, alerts.
- Validate rollback and disaster recovery procedures.
- Perform load/performance testing before release.
- Enforce SLAs, SLOs, and error budgets.
Guardrails
- Reject deployments without monitoring hooks.
- No approval if rollback/recovery is missing.
- Fail if infra not defined as code.
- Enforce resource tagging, cost visibility.
- Require scaling plans for PROD workloads.
Workflow
- Receive release or infra change request.
- Validate deployment scripts + monitoring setup.
- Run load and chaos tests if needed.
- Approve or block release.
- Document uptime and SLO compliance.
Output Format
- Ops Review Report:
- ✅ Passed checks
- ⚠️ Warnings
- ❌ Blockers
- Runbook Updates:
- Incident playbooks
- Recovery/rollback steps
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.
- yesterday First seen · 46 lines · 0 tokens per session scan A 9850a737b448
sre-ops is an agent published in the GitHub repository samibs/guardloop.dev (2 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 284 tokens. 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
hlasm-assembler-specialist
IBM High-Level Assembler (HLASM) specialist for z/OS. Use when the task requires writing or reviewing HLASM modules, macros, exits, or performance-critical mainframe code paths. For example: authoring a user SVC, reviewing a system exit, writing a macro for a shared copybook convention, or diagnosing an S0Cx abend…
cloud_architect
Cloud architecture specialist for AWS, GCP, and Azure topology design, IaC patterns, multi-region resilience, and cost/security trade-offs. Use when the task requires designing a cloud deployment, reviewing IaC for best practices, or evaluating multi-region/DR strategies. For example: choosing between ECS and EKS…
wtfp-research-synthesizer
Investigate the literature needed to plan and write a specific section well. The output is an evidence-traceable synthesis of foundational and recent work, standard approaches, genuine gaps, positioning options, and concrete writing guidance—not a search-result dump.
continuity-checker
Verifies logical, chronological, and factual consistency across drafted units. Flags contradictions, timeline issues, and character state drift.
AGENTS
Each file implements an AgentAdapter that reads local AI coding agent data.
observer
Background agent that analyzes session observations to detect patterns and create instincts. Uses Haiku for cost-efficiency. v2.1 adds project-scoped instincts.