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 skills add aws/tools-for-devops-agent --skill aws-eks-healthdashboardgit 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/aws-eks-healthdashboard)<a href="https://agentmods.dev/skills/aws/tools-for-devops-agent/aws-eks-healthdashboard"><img src="https://agentmods.dev/badge/skills/aws/tools-for-devops-agent/aws-eks-healthdashboard/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aws/tools-for-devops-agent/aws-eks-healthdashboard"><img src="https://agentmods.dev/badge/skills/aws/tools-for-devops-agent/aws-eks-healthdashboard.svg" alt="Reviewed on agentmods" width="80" 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.00235 | $0.04022 |
| Opus 5.5 | $0.00094 | $0.01609 |
| Sonnet 5.5 | $0.00047 | $0.00804 |
| Haiku 4.5 | $0.00023 | $0.00402 |
Grade A, and why
aws-eks-healthdashboard 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 today.
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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EKS Health Dashboard — DevOps Agent Skill
What this skill is
A focused, read-only EKS health monitor. It answers "is this cluster healthy right now?" across three domains and grades every signal it can observe:
- Cluster, Version & Add-on Health — cluster status +
health.issues, Kubernetes version & extended-support state, EKS managed add-on health (DEGRADED/failed +health.issues), whether core components (CoreDNS/kube-proxy/VPC CNI/CSI) are actually running, EKS Cluster Insights (upgrade/config/rollback), and Node Monitoring Agent enablement (CA-series). - Control Plane Health — etcd size/growth, APF throttling, API-server 5xx + LIST latency, write-path/verb latency, apiserver outbound-client errors, watch pressure, KCM backpressure, scheduler lag, eviction stalls (CP1–CP11 + the metric-native CP-M1–CP-M9). The control plane is AWS-managed, so these come from CloudWatch Logs Insights (audit log) + CloudWatch metrics, never kubectl.
- Node & Data-Plane Health — node conditions, node & pod utilization, EC2 instance status, ENA network allowances, EBS volume performance, NAT gateway, CoreDNS, Karpenter, Node Monitoring Agent conditions, a workload/pod health rollup, and the AWS-side nodegroup/registration facts (NH-series).
It reviews all available metrics: it detects which observability sources are enabled and fans
out across them (CloudWatch Logs, Container Insights, native EKS metrics, AMP / in-cluster
Prometheus, Datadog / New Relic / Dynatrace / Splunk), cross-validating where more than one covers
a signal. Output is a health dashboard artifact, not a best-practices audit — for the full
9-pillar review use the aws-eks-operations-review skill.
Read this skill and the reference files it names in full — do not distill/summarize them; the queries, thresholds, and check definitions live in the reference files. Load each with the runtime's resource-reading tool (in AWS DevOps Agent,
read_skill_resource).
What ships with it
60 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 77 B
- CHANGELOG.md 9.7 KB
- evals/best-practices/v1/benchmark.json 6.2 KB
- evals/best-practices/v1/iteration-1/best-practices-tests-results.json 9.8 KB
- evals/best-practices/v1/iteration-2/best-practices-tests-results.json 9.7 KB
- evals/best-practices/v1/iteration-3/best-practices-tests-results.json 9.9 KB
- evals/evals.json 22 KB
- evals/functional/v1/benchmark.json 273 KB
- evals/functional/v1/evals.json 22 KB
- evals/functional/v1/iteration-1/eks-health-cluster-confirmation-gate/with_skill/functional-tests-results.json 2.9 KB
- evals/functional/v1/iteration-1/eks-health-cluster-confirmation-gate/with_skill/outputs/journal_records.json 25 KB
- evals/functional/v1/iteration-1/eks-health-cluster-confirmation-gate/without_skill/functional-tests-results.json 1.5 KB
- evals/functional/v1/iteration-1/eks-health-cluster-confirmation-gate/without_skill/outputs/journal_records.json 3.9 KB
- evals/functional/v1/iteration-1/eks-health-control-plane-source/with_skill/functional-tests-results.json 4.4 KB
- evals/functional/v1/iteration-1/eks-health-control-plane-source/with_skill/outputs/journal_records.json 28 KB
- evals/functional/v1/iteration-1/eks-health-control-plane-source/without_skill/functional-tests-results.json 4.1 KB
- evals/functional/v1/iteration-1/eks-health-control-plane-source/without_skill/outputs/journal_records.json 38 KB
- evals/functional/v1/iteration-1/eks-health-dashboard-vs-audit-boundary/with_skill/functional-tests-results.json 2.8 KB
- evals/functional/v1/iteration-1/eks-health-dashboard-vs-audit-boundary/with_skill/outputs/journal_records.json 27 KB
- evals/functional/v1/iteration-1/eks-health-dashboard-vs-audit-boundary/without_skill/functional-tests-results.json 3.3 KB
- evals/functional/v1/iteration-1/eks-health-dashboard-vs-audit-boundary/without_skill/outputs/journal_records.json 18 KB
- evals/functional/v1/iteration-1/eks-health-no-runtime-files/with_skill/functional-tests-results.json 3.3 KB
- evals/functional/v1/iteration-1/eks-health-no-runtime-files/with_skill/outputs/journal_records.json 26 KB
- evals/functional/v1/iteration-1/eks-health-no-runtime-files/without_skill/functional-tests-results.json 4.7 KB
- evals/functional/v1/iteration-1/eks-health-no-runtime-files/without_skill/outputs/journal_records.json 18 KB
- evals/functional/v1/iteration-1/eks-health-read-only-contract/with_skill/functional-tests-results.json 3.0 KB
- evals/functional/v1/iteration-1/eks-health-read-only-contract/with_skill/outputs/journal_records.json 27 KB
- evals/functional/v1/iteration-1/eks-health-read-only-contract/without_skill/functional-tests-results.json 1.9 KB
- evals/functional/v1/iteration-1/eks-health-read-only-contract/without_skill/outputs/journal_records.json 33 KB
- evals/functional/v1/iteration-1/eks-health-scenario-429-workload-low-informational/with_skill/functional-tests-results.json 4.2 KB
- evals/functional/v1/iteration-1/eks-health-scenario-429-workload-low-informational/with_skill/outputs/journal_records.json 38 KB
- evals/functional/v1/iteration-1/eks-health-scenario-429-workload-low-informational/without_skill/functional-tests-results.json 7.5 KB
- evals/functional/v1/iteration-1/eks-health-scenario-429-workload-low-informational/without_skill/outputs/journal_records.json 61 KB
- evals/functional/v1/iteration-1/eks-health-scenario-cluster-insights-not-cp/with_skill/functional-tests-results.json 3.5 KB
- evals/functional/v1/iteration-1/eks-health-scenario-cluster-insights-not-cp/with_skill/outputs/journal_records.json 27 KB
- evals/functional/v1/iteration-1/eks-health-scenario-cluster-insights-not-cp/without_skill/functional-tests-results.json 4.1 KB
- evals/functional/v1/iteration-1/eks-health-scenario-cluster-insights-not-cp/without_skill/outputs/journal_records.json 27 KB
- evals/functional/v1/iteration-1/eks-health-scenario-confidence-contract/with_skill/functional-tests-results.json 3.2 KB
- evals/functional/v1/iteration-1/eks-health-scenario-confidence-contract/with_skill/outputs/journal_records.json 37 KB
- evals/functional/v1/iteration-1/eks-health-scenario-confidence-contract/without_skill/functional-tests-results.json 3.9 KB
- evals/functional/v1/iteration-1/eks-health-scenario-confidence-contract/without_skill/outputs/journal_records.json 11 KB
- evals/functional/v1/iteration-1/eks-health-scenario-dashboard-sections/with_skill/functional-tests-results.json 5.1 KB
- evals/functional/v1/iteration-1/eks-health-scenario-dashboard-sections/with_skill/outputs/journal_records.json 45 KB
- evals/functional/v1/iteration-1/eks-health-scenario-dashboard-sections/without_skill/functional-tests-results.json 3.9 KB
- evals/functional/v1/iteration-1/eks-health-scenario-dashboard-sections/without_skill/outputs/journal_records.json 48 KB
- evals/functional/v1/iteration-1/eks-health-scenario-empty-query-not-pass/with_skill/functional-tests-results.json 3.2 KB
- evals/functional/v1/iteration-1/eks-health-scenario-empty-query-not-pass/with_skill/outputs/journal_records.json 37 KB
- evals/functional/v1/iteration-1/eks-health-scenario-empty-query-not-pass/without_skill/functional-tests-results.json 5.2 KB
- evals/functional/v1/iteration-1/eks-health-scenario-empty-query-not-pass/without_skill/outputs/journal_records.json 7.6 KB
- evals/functional/v1/iteration-1/eks-health-scenario-etcd-growth-not-full/with_skill/functional-tests-results.json 3.6 KB
- evals/functional/v1/iteration-1/eks-health-scenario-etcd-growth-not-full/with_skill/outputs/journal_records.json 37 KB
- evals/functional/v1/iteration-1/eks-health-scenario-etcd-growth-not-full/without_skill/functional-tests-results.json 4.4 KB
- evals/functional/v1/iteration-1/eks-health-scenario-etcd-growth-not-full/without_skill/outputs/journal_records.json 47 KB
- evals/functional/v1/iteration-1/eks-health-scenario-findings-no-invented-thresholds/with_skill/functional-tests-results.json 3.8 KB
- evals/functional/v1/iteration-1/eks-health-scenario-findings-no-invented-thresholds/with_skill/outputs/journal_records.json 43 KB
- evals/functional/v1/iteration-1/eks-health-scenario-findings-no-invented-thresholds/without_skill/functional-tests-results.json 4.5 KB
- evals/functional/v1/iteration-1/eks-health-scenario-findings-no-invented-thresholds/without_skill/outputs/journal_records.json 46 KB
- evals/functional/v1/iteration-1/eks-health-scenario-logging-disabled-na-not-pass/with_skill/functional-tests-results.json 4.8 KB
- evals/functional/v1/iteration-1/eks-health-scenario-logging-disabled-na-not-pass/with_skill/outputs/journal_records.json 70 KB
- evals/functional/v1/iteration-1/eks-health-scenario-logging-disabled-na-not-pass/without_skill/functional-tests-results.json 4.2 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.
- today First seen · 137 lines · 235 tokens per session scan A f691efb6eccf
aws-eks-healthdashboard is a skill published in the GitHub repository aws/tools-for-devops-agent (116 stars, last pushed today), licensed Apache-2.0. It adds 235 tokens to every session and 4,022 once invoked, about $0.0009 per session on Opus 5.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-10-28.
Other skills, from other repositories
cis-aws-compute-3.1
Ensure Amazon ECS task definitions using 'host' network mode do not allow privileged or root user access to the host.
cis-aws-compute-3.13
Ensure only trusted images are used with Amazon ECS.
cis-aws-compute-3.3
Ensure Amazon ECS task definitions do not have 'pidMode' set to 'host'.
cis-aws-compute-3.5
Ensure 'readonlyRootFilesystem' is set to 'true' for Amazon ECS task definitions.
cis-aws-compute-3.6
Ensure secrets are not passed as container environment variables in Amazon ECS task definitions.
cis-aws-compute-3.10
Ensure Amazon ECS services are tagged.