eks-operation-review

eks-operation-review is a skill for Claude Code, Codex from aws/tools-for-devops-agent. It costs 99 tokens per session (4,097 once invoked), scanned A, original, Apache-2.0.

A review procedure for Amazon EKS, Amazon’s managed service for running Kubernetes clusters. Kubernetes is software that runs and coordinates containerised applications.

In plain words
What is it for?
It helps audit cluster configuration, reliability, security, cost, networking, scalability, and readiness for upgrades against AWS best practices.
Why use it?
It checks whether an EKS environment is ready to operate safely and reliably, including its security, cost, networking, scaling, and upgrade concerns.

Skill for Claude CodeCodex

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 skills/aws/tools-for-devops-agent/eks-operation-review
Any agent
npx skills add aws/tools-for-devops-agent --skill eks-operation-review
Clone the repo
git clone --depth 1 https://github.com/aws/tools-for-devops-agent

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for eks-operation-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/aws/tools-for-devops-agent/eks-operation-review.svg)](https://agentmods.dev/skills/aws/tools-for-devops-agent/eks-operation-review)
Your own site
<a href="https://agentmods.dev/skills/aws/tools-for-devops-agent/eks-operation-review"><img src="https://agentmods.dev/badge/skills/aws/tools-for-devops-agent/eks-operation-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 99 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,097 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.00099 $0.04097
Opus 5 $0.00049 $0.02048
Sonnet 5 $0.00020 $0.00819
Haiku 4.5 $0.00010 $0.00410

Measured 4d ago against content hash 3639faf1eec7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

eks-operation-review 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 4d 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.

skills/eks-operation-review/SKILL.md · 338 lines

How it starts

The opening of the file, as written. The whole thing — 338 lines — stays where its author put it; the contents beside it link to each section on GitHub.

EKS Operational Review

Conduct a comprehensive operational review of Amazon EKS clusters aligned with the EKS Best Practices Guide.

When to Use

Activate this skill when the user asks to:

  • Review, audit, or assess EKS clusters
  • Check EKS best practices compliance
  • Evaluate EKS security, cost, reliability, networking, or scalability
  • Perform an EKS operational readiness review
  • Investigate EKS cluster health or configuration

Step 1: Identify Target Clusters

Ask the user which EKS clusters to review. Accept:

  • Specific cluster names and regions
  • "all clusters" in specific regions
  • "all clusters in all regions"

Use the EKS topology data available in the Agent Space to identify clusters. Query CloudWatch and AWS APIs to discover clusters:

  • List EKS clusters across the configured account regions
  • For each cluster, collect configuration details

Step 2: Collect Cluster Configuration

Data source priority: If Kubernetes API access is available (via connected MCP servers such as kubernetes-mcp-server, EKS MCP server, or direct K8s API tools), use it FIRST to get live cluster state. K8s API provides the most accurate, real-time data. Fall back to AWS APIs and CloudWatch only for data not available via K8s API.

K8s API tools (use first when available):

  • resources_list / resources_get — list/read any K8s resource by apiVersion and kind
  • pods_list / pods_get / pods_log / pods_top — pod operations
  • nodes_top — node resource usage
  • events_list — K8s events
  • configuration_contexts_list — available cluster contexts

For EACH cluster, gather the following data. Try K8s API first, then AWS API as fallback:

2.1 EKS Cluster Config

AWS API (no K8s equivalent): Kubernetes version, platform version, control plane logging, secrets encryption, endpoint access, authentication mode, access entries, Auto Mode, tags

2.2 Node Groups & Compute

K8s API first:

  • resources_list(apiVersion="v1", kind="Node") — live node list with labels, capacity, allocatable, conditions
  • nodes_top — actual CPU/memory usage per node
  • resources_list(apiVersion="karpenter.sh/v1", kind="NodePool") — Karpenter NodePools
  • resources_get(apiVersion="karpenter.sh/v1", kind="NodePool", name=<name>) — full NodePool spec (consolidation, limits, disruption, requirements)
  • resources_list(apiVersion="karpenter.k8s.aws/v1", kind="EC2NodeClass") — EC2NodeClasses
  • resources_get(apiVersion="karpenter.k8s.aws/v1", kind="EC2NodeClass", name=<name>) — full spec (amiFamily, blockDeviceMappings, metadataOptions, subnets, SGs)

Read the full file on GitHub · 338 lines

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. 4d ago First seen · 338 lines · 99 tokens per session scan A 3639faf1eec7

Subscribe to this mod's changes

eks-operation-review is a skill published in the GitHub repository aws/tools-for-devops-agent (45 stars, last pushed today), licensed Apache-2.0. It adds 99 tokens to every session and 4,097 once invoked, about $0.0005 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-30.