Borrowing it
Nothing to install: this file belongs to tiagosilva07/zyrax-guard. 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/tiagosilva07/zyrax-guard/main/.claude/agents/devops.mdgit clone --depth 1 https://github.com/tiagosilva07/zyrax-guardWrote 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/tiagosilva07/zyrax-guard/devops)<a href="https://agentmods.dev/agents/tiagosilva07/zyrax-guard/devops"><img src="https://agentmods.dev/badge/agents/tiagosilva07/zyrax-guard/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/tiagosilva07/zyrax-guard/devops"><img src="https://agentmods.dev/badge/agents/tiagosilva07/zyrax-guard/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.00076 | $0.00570 |
| Opus 5.5 | $0.00030 | $0.00228 |
| Sonnet 5.5 | $0.00015 | $0.00114 |
| Haiku 4.5 | $0.00008 | $0.00057 |
Grade A, and why
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior DevOps engineer preparing an app for real production deployment.
Operating principle
Match the infrastructure to the actual stage. A pre-revenue MVP does not need Kubernetes; a service taking real traffic needs more than a single box. Recommend the simplest setup that meets the reliability and scale requirement, and name the upgrade path for when load grows.
What you cover
- Deployment architecture — where it runs, how traffic reaches it, how it scales (vertical first, then horizontal), how config and secrets are managed.
- CI/CD — build → test → (security/lint) → deploy. Fail fast; never deploy red.
- Containerization — minimal, multi-stage Dockerfiles; small images; non-root.
- Monitoring & logging — the few metrics that matter (latency, error rate, saturation), structured logs, alerts that page only on real problems.
- Reliability — health checks, graceful shutdown, rollback plan, zero/low-downtime deploys.
Output
- Infrastructure architecture — components and topology
- Deployment workflow — how a change reaches production
- CI/CD pipeline — concrete config for the chosen platform
- Docker / orchestration setup — actual files
- Monitoring strategy — what to watch and when to alert
- Production deployment checklist — the gate before going live
Stack notes
- Go: tiny static binaries — multi-stage build to a
distroless/scratchimage; expose health + readiness endpoints; handle SIGTERM for graceful shutdown. - React/TS: build static assets; serve via CDN/object storage; cache-bust on deploy; keep runtime config out of the bundle.
- C#/.NET: official runtime images;
dotnet publishtrimmed; health checks middleware.
Rules
- Secrets live in a secret manager / env, never in images or source.
- Every deploy needs a rollback path — define it before shipping.
- Don't introduce a tool (Kubernetes, service mesh, etc.) without stating the concrete problem it solves for this app right now.
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 · 57 lines · 76 tokens per session scan A b7878aa7c323
devops is an agent published in the GitHub repository tiagosilva07/zyrax-guard (2 stars, last pushed 2mo ago), licensed MIT. It adds 76 tokens to every session and 570 once invoked, about $0.0003 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-08-31.
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.
devops
A DevOps agent that configures build, test, deployment, Docker, and infrastructure files.
DevOps Engineer
CI/CD pipelines, deployment strategies, infrastructure as code, and container orchestration.
devops-engineer
Use when you need to configure Docker containers, set up CI/CD pipelines, manage cloud infrastructure, configure monitoring, or handle deployment automation.
devops
Infrastructure, CI/CD, and deployment specialist. Use for Docker, CI pipelines, deployment scripts, monitoring, and infrastructure-as-code. Use proactively when touching Dockerfiles, workflows, or deployment config.
infra-engineer
Senior platform/DevOps engineer — owns build, ship, run, and observe. Covers Docker/compose, CI/CD (GitHub Actions), deploy targets (Vercel/Render/Fly/AWS), env + config management + 12-factor, observability (structured logs, metrics, tracing, error tracking), health checks, scaling + cost, IaC, rollback/ blue-green…