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/hk-hub/agentskills/devops-engineernpx skills add HK-hub/AgentSkills --skill devops-engineergit clone --depth 1 https://github.com/HK-hub/AgentSkillsWrote 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/hk-hub/agentskills/devops-engineer)<a href="https://agentmods.dev/skills/hk-hub/agentskills/devops-engineer"><img src="https://agentmods.dev/badge/skills/hk-hub/agentskills/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.01345 |
| Opus 5 | $0.00053 | $0.00673 |
| Sonnet 5 | $0.00021 | $0.00269 |
| Haiku 4.5 | $0.00011 | $0.00135 |
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 3d 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 This is a copy
92% identical to devops-engineer — 10 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 145 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 - Deploy - 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 |
| 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
8 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/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.
- 3d ago First seen · 145 lines · 107 tokens per session scan A b119ff7ab092
devops-engineer is a skill published in the GitHub repository HK-hub/AgentSkills (6 stars, last pushed 19d ago), licensed MIT. It adds 107 tokens to every session and 1,345 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). It is 92% identical to devops-engineer, differing in 10 lines, and is treated as a copy.
Other skills, from other repositories
infrastructure
Operate and maintain a project's deployment and infrastructure from the primary session: environment topology, Docker and Compose, CI/CD, Dokploy, domains and TLS, observability, and the operational layer of PostgreSQL or Redis. Uses a project-owned infrastructure map and verifies live state before consequential…
mainframe-infrastructure
Operate, diagnose, change, or verify project deployment and infrastructure from the primary Codex task. Use for environment topology, Dockerfiles and Compose, CI/CD, deployment and rollback, Dokploy, domains and TLS, observability, backups, managed databases, PostgreSQL or Redis operations, and credentials consumed by…
DevOps Pipeline Builder
Design and implement CI/CD pipelines, Docker configurations, deployment strategies, and infrastructure automation with production-ready patterns.
ci-debug-workflow
Debug failing CI pipelines, containers, and reproduce bugs locally. Use when CI is red, containers won't start, or need to reproduce bugs.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications.
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.