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/aws/tools-for-devops-agent/eks-operation-reviewnpx skills add aws/tools-for-devops-agent --skill eks-operation-reviewgit clone --depth 1 https://github.com/aws/tools-for-devops-agentWrote 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/aws/tools-for-devops-agent/eks-operation-review)<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>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 | $0.00099 | $0.04097 |
| Opus 5 | $0.00049 | $0.02048 |
| Sonnet 5 | $0.00020 | $0.00819 |
| Haiku 4.5 | $0.00010 | $0.00410 |
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.
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 kindpods_list/pods_get/pods_log/pods_top— pod operationsnodes_top— node resource usageevents_list— K8s eventsconfiguration_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, conditionsnodes_top— actual CPU/memory usage per noderesources_list(apiVersion="karpenter.sh/v1", kind="NodePool")— Karpenter NodePoolsresources_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")— EC2NodeClassesresources_get(apiVersion="karpenter.k8s.aws/v1", kind="EC2NodeClass", name=<name>)— full spec (amiFamily, blockDeviceMappings, metadataOptions, subnets, SGs)
What ships with it
11 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.
- .skilleval.yaml 76 B
- CHANGELOG.md 41 B
- evals/benchmark.json 26 KB
- evals/eval_queries.json 713 B
- evals/evals.json 3.0 KB
- evals/files/cluster-context.json 103 B
- evals/report.json 1.6 KB
- evals/trigger_report.json 2.6 KB
- README.md 13 KB
- references/best-practices-checklist.md 2.5 KB
- references/metrics-thresholds.md 2.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.
- 4d ago First seen · 338 lines · 99 tokens per session scan A 3639faf1eec7
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.
Other skills, from other repositories
prowler-compliance
Creates, syncs, audits and manages Prowler compliance frameworks end-to-end. Covers the two supported JSON schemas (universal multi-provider and legacy per-provider), the SDK model tree (legacy attribute classes, universal ComplianceFramework, ConfigRequirements guardrails), output formatters (legacy per-framework +…
jsonapi
Strict JSON:API v1.1 specification compliance. Trigger: When creating or modifying API endpoints, reviewing API responses, or validating JSON:API compliance.
prowler-compliance-review
Reviews Pull Requests that add or modify compliance frameworks. Trigger: When reviewing PRs with compliance framework changes, CIS/NIST/PCI-DSS additions, or compliance JSON files.
prowler-readme-table
Updates the "Prowler at a Glance" table in README.md with accurate provider statistics. Trigger: When updating README.md provider stats, checks count, services count, compliance frameworks, or categories.
notion
Notion workspace integration for searching pages, managing databases, creating postmortems, and exporting RCA findings.
datadog
Datadog monitoring integration for querying logs, metrics, monitors, events, traces, hosts, and incidents during RCA investigations.