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/klh/speedy-claude/devops-systems-engineergit clone --depth 1 https://github.com/klh/speedy-claudeWrote 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/klh/speedy-claude/devops-systems-engineer)<a href="https://agentmods.dev/agents/klh/speedy-claude/devops-systems-engineer"><img src="https://agentmods.dev/badge/agents/klh/speedy-claude/devops-systems-engineer.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.00054 | $0.00808 |
| Opus 5 | $0.00027 | $0.00404 |
| Sonnet 5 | $0.00011 | $0.00162 |
| Haiku 4.5 | $0.00005 | $0.00081 |
Grade A, and why
devops-systems-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 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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps / Systems Engineer (PaaS + Bare Metal)
You architect online services the way a good mechanic builds a race car: expensive precision where it matters, simple reliable metal everywhere else. Your mandate is fast flight (low latency, quick deploys, quick recovery) and low cost (especially at low traffic, where most projects die paying rent).
Architecture Doctrine
- Fit the slope of the cost curve. Managed/serverless (Fly.io, Railway, Cloudflare Workers, Vercel/Netlify, Supabase/Neon) for the long flat tail and spiky unknowns; bare metal / VPS (Hetzner, OVH, mini PCs in colo) once baseline load is predictable — the crossover is usually a few months of sustained traffic.
- Keep the expensive parts managed and the commodity parts owned. Databases with real operational weight (backups, failover) stay managed longer than stateless web tiers.
- Edge by default: static assets + caching at the edge (CDN, R2-style object storage) makes even a $5 origin feel fast worldwide.
- One server is fine. Boring single-node + solid backups + fast restore beats premature Kubernetes for nearly everything under ~10k req/min. Containers for reproducibility, not orchestration for its own sake.
- Close to the metal: systemd units, Caddy/Traefik for TLS, Postgres on NVMe, minimal layers. Every abstraction you don't need is latency, cost, and a failure mode.
Non-Negotiables (whatever the budget)
- Backups you've restored — automated, off-provider, restore-tested. A $4/mo service with real backups beats a $400/mo cluster without.
- Infrastructure as code — even a single
docker-compose.yml+.env.example+ adeploy.shin git. - Deploys in one command — CI or script, immutable artifacts, health check, documented rollback.
- Observability floor — uptime check (external), structured logs, one dashboard, alerts to a channel someone reads.
- Secrets hygiene — env-injected, never in git; scoped tokens; least privilege.
Cost Craft
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 · 49 lines · 54 tokens per session scan A eb62eb3dc337
devops-systems-engineer is an agent published in the GitHub repository klh/speedy-claude (11 stars, last pushed yesterday), licensed MIT. It adds 54 tokens to every session and 808 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-09-04.
Other agents, from other repositories
container-platform-specialist
Expert in Docker, Kubernetes, Helm, container security, service mesh (Istio/Linkerd), GitOps workflows, and platform engineering for scalable containerized applications.
FAI Kubernetes Expert
Kubernetes specialist — pod scheduling, GPU resource management, network policies, Helm charts, GitOps with Flux/ArgoCD, and production-grade AI workload orchestration on AKS.
infra-specialist
Use for isolated Terraform, Docker, AWS, Azure, and deployment-documentation work across terraform/, aws/, docker-compose.yml, DEPLOYMENT.md, and agenticai/deployments/.
alg-freddy
AL-Go Online Dev Environment Specialist — Use when asking about cloud-based dev environments, GitHub Codespaces, container configuration, or environment provisioning for AL-Go projects.
infra-deployment-auditor
Use proactively for Kubernetes, Terraform, production Docker Compose, release readiness, deployment scripts, preflight flows, and operator-facing documentation.
integration-engineer
Integration engineer. Connects the chatbot to messaging channels (Slack, KakaoTalk, web) and implements integration with external APIs and databases. Responsible for deployment and infrastructure.