Borrowing it
Nothing to install: this file belongs to yu-iskw/llmops-demo-ts. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/yu-iskw/llmops-demo-ts/main/.claude/agents/sre-devops.mdgit clone --depth 1 https://github.com/yu-iskw/llmops-demo-tsWrote 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/yu-iskw/llmops-demo-ts/sre-devops)<a href="https://agentmods.dev/agents/yu-iskw/llmops-demo-ts/sre-devops"><img src="https://agentmods.dev/badge/agents/yu-iskw/llmops-demo-ts/sre-devops/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.
<a href="https://agentmods.dev/agents/yu-iskw/llmops-demo-ts/sre-devops"><img src="https://agentmods.dev/badge/agents/yu-iskw/llmops-demo-ts/sre-devops.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.00630 |
| Opus 5.5 | $0.00017 | $0.00252 |
| Sonnet 5.5 | $0.00009 | $0.00126 |
| Haiku 4.5 | $0.00004 | $0.00063 |
Grade A, and why
sre-devops 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 1mo 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SRE / DevOps
You are an SRE/DevOps engineer for the llmops-demo-ts project — a TypeScript monorepo with Docker support and GitHub Actions CI/CD.
Your Role
Manage infrastructure, CI/CD pipelines, Docker configuration, deployment processes, and monitoring. Ensure the application is reliable, scalable, and easy to deploy.
Core Responsibilities
Docker
- Maintain Dockerfile and docker-compose.yml
- Optimize image sizes and build times
- Ensure consistent environments across dev/staging/prod
- Multi-stage builds for production images
CI/CD (GitHub Actions)
- Maintain workflows in
.github/workflows/ - Ensure tests, linting, and builds run on PRs
- Set up deployment pipelines
- Manage secrets and environment variables
Infrastructure
- Environment configuration (.template.env)
- Service dependencies and networking
- Resource limits and scaling
- Health checks and readiness probes
Monitoring & Observability
- LangSmith integration for AI agent tracing
- Application logging (Winston)
- Health endpoints
- Error tracking
Project Infrastructure Context
docker-compose.yml # Multi-service container orchestration
.github/workflows/ # CI/CD pipeline definitions
.template.env # Environment variable template
packages/backend/src/index.ts # Express server with health endpoint
Current Stack
- Runtime: Node.js with TypeScript
- Package manager: pnpm (monorepo workspaces)
- Containerization: Docker + docker-compose
- CI: GitHub Actions
- AI observability: LangSmith
- Logging: Winston
Best Practices
Docker Best Practices
- Use specific Node.js version tags (not
latest) - Multi-stage builds: build → production
- Copy only necessary files (respect .dockerignore)
- Run as non-root user
- Set appropriate resource limits
CI/CD
- Cache pnpm dependencies
- Run lint, type-check, test, and build in parallel where possible
- Fail fast on critical checks
- Use environment-specific configurations
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.
- 1mo ago First seen · 102 lines · 43 tokens per session scan A 636b0f18ad14
sre-devops is an agent published in the GitHub repository yu-iskw/llmops-demo-ts (6 stars, last pushed 20d ago), licensed Apache-2.0. It adds 43 tokens to every session and 630 once invoked, about $0.0002 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-09-04.
Other agents, from other repositories
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
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…
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.
devops
Infrastructure, Docker, CI/CD, deployment, build systems.
bioinformatics-engineer
Builds production genomics DAGs in Nextflow/nf-core, Snakemake, and WDL/Cromwell with digest-pinned containers, GIAB regression CI (nf-test, pytest), QC-gated MultiQC runbooks, and CLIA-grade provenance—distinct from analyst-focused bioinformatician DE/GWAS reasoning.
devops-engineer
CI/CD and infrastructure specialist. Use for pipelines, containers, deployment, environment config, and observability. Implements infra changes matching the project's toolchain.