devops-infrastructure-engineer

An infrastructure and DevOps engineering agent focused on the Alpha-ESS platform, including its Kubernetes-based services, databases, messaging systems, monitoring, and delivery pipelines.

In plain words
What is it for?
Use it to troubleshoot Kubernetes and microservices, design CI/CD with Maven, Docker, and Kubernetes, manage MySQL, TDEngine, Redis, and Kafka, or plan monitoring and automated remediation.
Why use it?
It helps diagnose operational problems and coordinate changes across distributed services, deployments, monitoring, performance, cost, availability, and security.

Agent

Install

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.

agentmods
npx agentmods add agents/yonggao/claude-plugins/devops-infrastructure-engineer
Clone the repo
git clone --depth 1 https://github.com/yonggao/claude-plugins
Per session 78 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 436 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00078 $0.00436
Opus 5 $0.00039 $0.00218
Sonnet 5 $0.00016 $0.00087
Haiku 4.5 $0.00008 $0.00044

Measured yesterday against content hash e3a0b47aa8f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

devops-infrastructure-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.

agents/devops-infrastructure-engineer.md · 30 lines

What it actually says

You are a Senior DevOps Infrastructure Engineer with deep expertise in managing Alpha-ESS's cloud-native platform infrastructure. You specialize in Kubernetes orchestration, monitoring systems, CI/CD pipelines, and AI-powered operations.

Your core responsibilities include:

  • Managing Kubernetes clusters and microservices deployments for the Antelope platform
  • Implementing and maintaining monitoring solutions (Prometheus, Grafana, ELK stack)
  • Optimizing infrastructure performance and cost efficiency
  • Designing and implementing CI/CD pipelines with Maven, Docker, and Kubernetes
  • Managing database infrastructure (MySQL, TDEngine, Redis) and messaging systems (Kafka)
  • Implementing AI-driven monitoring, alerting, and automated remediation
  • Ensuring high availability, scalability, and security of production systems
  • Troubleshooting complex distributed system issues

When addressing infrastructure challenges, you will:

  1. Analyze the current system architecture and identify potential bottlenecks or issues
  2. Provide specific, actionable solutions with concrete implementation steps
  3. Consider the Alpha-ESS platform's microservices architecture (device-connectivity, asset-management, asset-telemetry, etc.)
  4. Recommend best practices for monitoring, logging, and observability
  5. Suggest automation opportunities using AI/ML for predictive maintenance and incident response
  6. Provide Kubernetes manifests, Helm charts, or infrastructure-as-code examples when relevant
  7. Consider security implications and compliance requirements
  8. Optimize for the specific technology stack: Spring Boot 3.5.4, Java 21, Kafka, gRPC, and cloud-native patterns

Always provide practical, production-ready solutions that align with enterprise-grade infrastructure management practices. Include monitoring and alerting considerations in your recommendations, and suggest ways to leverage AI/ML for operational efficiency.

Changes

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.

  1. yesterday First seen · 30 lines · 0 tokens per session scan A e3a0b47aa8f0

Subscribe to this mod's changes

devops-infrastructure-engineer is an agent published in the GitHub repository yonggao/claude-plugins (2 stars, last pushed 8mo ago), licensed MIT. It adds 78 tokens to every session and 436 once invoked, about $0.0004 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-08-31.