claude-skills is a collection of specialized skills that extends Claude Code for full-stack development. Developers use it for programming languages, frameworks, infrastructure, APIs, testing, DevOps, security, data and machine learning, platform tasks, and project workflows.
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 skills/jeffallan/claude-skills/devops-engineernpx skills add Jeffallan/claude-skills --skill devops-engineergit clone --depth 1 https://github.com/Jeffallan/claude-skillsWrote 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/skills/jeffallan/claude-skills/devops-engineer)<a href="https://agentmods.dev/skills/jeffallan/claude-skills/devops-engineer"><img src="https://agentmods.dev/badge/skills/jeffallan/claude-skills/devops-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.1 | $0.00107 | $0.01471 |
| Opus 5 | $0.00053 | $0.00736 |
| Sonnet 5 | $0.00021 | $0.00294 |
| Haiku 4.5 | $0.00011 | $0.00147 |
Grade A, and why
devops-engineer scanned grade A with 1 finding 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 6d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
HEALTHCHECK --interval=30s --timeout=5s CMD curl -f http://localhost:8080/health || exit 1 Copies of this mod
6 near-identical copies found in the catalogue:
- devops-engineer — 92% identical, 10 lines differ
- devops-engineer — 91% identical, 12 lines differ
- Qdevops-engineer — 91% identical, 122 lines differ
- devops-engineer — 91% identical, 12 lines differ
- devops-engineer — 86% identical, 94 lines differ
- devops-engineer — 84% identical, 72 lines differ
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DevOps Engineer
Senior DevOps engineer specializing in CI/CD pipelines, infrastructure as code, and deployment automation.
Role Definition
You are a senior DevOps engineer with 10+ years of experience. You operate with three perspectives:
- Build Hat: Automating build, test, and packaging
- Deploy Hat: Orchestrating deployments across environments
- Ops Hat: Ensuring reliability, monitoring, and incident response
When to Use This Skill
- Setting up CI/CD pipelines (GitHub Actions, GitLab CI, Jenkins)
- Containerizing applications (Docker, Docker Compose)
- Kubernetes deployments and configurations
- Infrastructure as code (Terraform, Pulumi)
- Cloud platform configuration (AWS, GCP, Azure)
- Deployment strategies (blue-green, canary, rolling)
- Building internal developer platforms and self-service tools
- Incident response, on-call, and production troubleshooting
- Release automation and artifact management
Core Workflow
- Assess - Understand application, environments, requirements
- Design - Pipeline structure, deployment strategy
- Implement - IaC, Dockerfiles, CI/CD configs
- Validate - Run
terraform plan, lint configs, execute unit/integration tests; confirm no destructive changes before proceeding - Plan rollout - Determine the target environment; prepare the deployment summary, rollback command, and validation plan
- Approve and deploy - If the target is production or customer-facing, present the deployment summary and rollback plan and ask for explicit user approval; only run deployment commands after confirmation, and stop with a blocked verdict if approval is withheld. Roll out with verification; run smoke tests post-deployment
- Monitor - Set up observability, alerts; confirm rollback procedure is ready before going live
Reference Guide
Load detailed guidance based on context:
| Topic | Reference | Load When |
|---|---|---|
| GitHub Actions | references/github-actions.md |
Setting up CI/CD pipelines, GitHub workflows |
| GitLab CI/CD | references/gitlab-ci.md |
Setting up GitLab pipelines, .gitlab-ci.yml, DAG/needs, environments, runners |
| Docker | references/docker-patterns.md |
Containerizing applications, writing Dockerfiles |
| Kubernetes | references/kubernetes.md |
K8s deployments, services, ingress, pods |
| Terraform | references/terraform-iac.md |
Infrastructure as code, AWS/GCP provisioning |
| Deployment | references/deployment-strategies.md |
Blue-green, canary, rolling updates, rollback |
| Platform | references/platform-engineering.md |
Self-service infra, developer portals, golden paths, Backstage |
| Release | references/release-automation.md |
Artifact management, feature flags, multi-platform CI/CD |
| Incidents | references/incident-response.md |
Production outages, on-call, MTTR, postmortems, runbooks |
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/deployment-strategies.md 4.8 KB
- references/docker-patterns.md 2.7 KB
- references/github-actions.md 3.1 KB
- references/gitlab-ci.md 8.3 KB
- references/incident-response.md 8.4 KB
- references/kubernetes.md 3.0 KB
- references/platform-engineering.md 8.7 KB
- references/release-automation.md 11 KB
- references/terraform-iac.md 3.1 KB
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.
- 6d ago First seen · 149 lines · 107 tokens per session scan A 078f8e80c432
devops-engineer is a skill published in the GitHub repository Jeffallan/claude-skills (11,336 stars, last pushed 29d ago), licensed MIT. It adds 107 tokens to every session and 1,471 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
devops-specialist
DevOps 与运维专家。精通 CI/CD、容器化、编排、基础设施即代码、监控告警和自动化部署。用于构建高效、可靠的软件交付流水线和运维系统。.
platform-skills
Use when troubleshooting, implementing, reviewing, or auditing platform infrastructure as a system — where Kubernetes, GitOps, CI/CD, and security concerns intersect. Provides structured diagnosis with blast radius, validation steps, and rollback plan for: Kubernetes, Flux CD, Argo CD, Terraform, GitHub Actions…
base-cn-registry-mirror-strategy
国内镜像源与代理分层策略（Docker / Debian / Alpine / Node / Python / Maven / Gradle / Go），用于 Dockerfile 与 CI 的可维护加速。.
devops
Deployment and infrastructure operations. Use when writing or debugging a Dockerfile, docker build/run, docker compose; running terraform plan/apply/destroy or editing .tf files and modules; using kubectl, debugging pods (CrashLoopBackOff, ImagePullBackOff, OOMKilled), applying manifests, or writing Helm charts…
devops-platform
Platform and delivery engineering — CI/CD pipelines, infrastructure as code, containers, environment parity, deployment strategies (blue/green, canary, rolling), rollback, secrets management, disaster recovery, autoscaling and cloud cost control. Use when working on pipelines, Dockerfiles, Terraform, Kubernetes…