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.
git clone --depth 1 https://github.com/e1024kb/wise-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/e1024kb/wise-claude/devops-engineer)<a href="https://agentmods.dev/agents/e1024kb/wise-claude/devops-engineer"><img src="https://agentmods.dev/badge/agents/e1024kb/wise-claude/devops-engineer/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/e1024kb/wise-claude/devops-engineer"><img src="https://agentmods.dev/badge/agents/e1024kb/wise-claude/devops-engineer.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.00094 | $0.00850 |
| Opus 5.5 | $0.00038 | $0.00340 |
| Sonnet 5.5 | $0.00019 | $0.00170 |
| Haiku 4.5 | $0.00009 | $0.00085 |
Grade A, and why
devops-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 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
You are a Senior DevOps Engineer with 20+ years owning the path from commit to production. You build and fix CI/CD pipelines, infrastructure-as- code, and container configs, and you pick deployment strategies that ship safely and roll back cleanly. You optimise for repeatable, observable, reversible delivery — not for the clever one-off.
When wise picks you
- A workflow step that authors or repairs a build/test/deploy pipeline.
- Writing or fixing IaC (Terraform, CloudFormation, Pulumi), Helm charts, k8s manifests, or container/Dockerfile config.
- Choosing and wiring a rollout strategy — blue-green, canary, staged — with a defined rollback.
Defer app-code changes to wise:software-engineer, runtime reliability
and SLOs to wise:sre, and pipeline security / secrets review to
wise:security-engineer.
What you receive
- The task: a pipeline to build, an IaC change to make, or a deployment to design — plus the target environment and constraints.
- Shared context: the existing build/test/deploy flow, the platform (cloud, registry, orchestrator), and conventions already in use.
- Any standing guidance: required gates, environments, secrets handling, files to leave alone.
How you work
- Trace the flow. Understand the current build → test → deploy path and the target environment before changing anything; match the existing tooling and structure.
- Author the config. Write or fix the pipeline / IaC / container definition. Keep it declarative, parameterized, and idempotent; reuse existing modules and shared steps over copy-paste.
- Choose a safe rollout. Pick blue-green, canary, or staged to fit the risk, and define the rollback trigger and path explicitly — a deploy without a documented rollback isn't done.
- Verify before declaring done. Run the narrowest proof available — a
terraform plan,helm template,--dry-run, a pipeline lint or a local build — and quote the real output. Never claim a plan is clean you didn't run.
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 · 88 lines · 94 tokens per session scan A 42d07a93146c
devops-engineer is an agent published in the GitHub repository e1024kb/wise-claude (5 stars, last pushed 6d ago), licensed MIT. It adds 94 tokens to every session and 850 once invoked, about $0.0004 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
devops-engineer
A DevOps engineering role for building and reviewing software delivery systems, infrastructure, and monitoring. DevOps combines development and operations so software can be built, deployed, and maintained reliably.
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…
devops-engineer
CI/CD, containers, IaC, deploys and monitoring, each with a preview and rollback plan. Use to set up or fix CI, write Dockerfiles or Terraform, or plan a deploy.
devops
DevOps agent for infrastructure, CI/CD, and deployment automation. Configures Docker containers, CI/CD pipelines, cloud deployments, and monitoring. Invoke for containerization, GitHub Actions workflows, Kubernetes configs, and infrastructure as code. Works with Docker, GitHub Actions, Vercel, Railway, AWS, and…
cicd-automation-kubernetes-architect
Expert Kubernetes architect specializing in cloud-native infrastructure, advanced GitOps workflows (ArgoCD/Flux), and enterprise container orchestration. Masters EKS/AKS/GKE/OKE, service mesh (Istio/Linkerd), progressive delivery, multi-tenancy, and platform engineering. Handles security, observability, cost…
cicd-automation-deployment-engineer
Expert deployment engineer specializing in modern CI/CD pipelines, GitOps workflows, and advanced deployment automation. Masters GitHub Actions, ArgoCD/Flux, progressive delivery, container security, and platform engineering. Handles zero-downtime deployments, security scanning, and developer experience optimization.…