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 cookieMonsterDev/agents-skills --skill aws-eks-docsgit clone --depth 1 https://github.com/cookieMonsterDev/agents-skillsWrote 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/cookiemonsterdev/agents-skills/aws-eks-docs)<a href="https://agentmods.dev/skills/cookiemonsterdev/agents-skills/aws-eks-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/aws-eks-docs/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/cookiemonsterdev/agents-skills/aws-eks-docs"><img src="https://agentmods.dev/badge/skills/cookiemonsterdev/agents-skills/aws-eks-docs.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.00096 | $0.01402 |
| Opus 5.5 | $0.00038 | $0.00561 |
| Sonnet 5.5 | $0.00019 | $0.00280 |
| Haiku 4.5 | $0.00010 | $0.00140 |
Grade A, and why
aws-eks-docs 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 1mo 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Amazon EKS questions are easy to answer from stale memory or generic Kubernetes advice that ignores AWS-specific control plane, IAM, and networking. Use this skill to ground answers in the official Amazon EKS documentation and return the closest authoritative page instead of improvising cloud-provider steps.
When to Use
Use this skill when the request is about:
- EKS concepts, architecture, and how EKS differs from self-managed Kubernetes
- Creating clusters, cluster IAM roles, and cluster endpoint access
- Managed node groups, self-managed nodes, and AWS Fargate profiles
- EKS Auto Mode and compute/storage automation
- Cluster add-ons (VPC CNI, CoreDNS, kube-proxy, EBS CSI, etc.)
- IAM Roles for Service Accounts (IRSA) and cluster access entries
- Networking: VPC, subnets, security groups, load balancers, and service mesh adjacency
- Storage on EKS: EBS, EFS, FSx, and S3 CSI drivers
- Observability: control plane logging, CloudWatch, Prometheus, and ADOT
- Upgrades, Kubernetes version lifecycle, and extended support
- EKS Capabilities (Argo CD, ACK, kro) and GitOps on EKS
- EKS Anywhere, hybrid nodes, and outpost deployments
- eksctl, CloudFormation, CDK, and Terraform patterns documented for EKS
- Troubleshooting cluster creation, node join, CNI, and API access errors
Do not use this skill for:
- Core Kubernetes API behavior with no EKS-specific context. Use
kubernetes-docsinstead. - AWS CLI install or global CLI options. Use
aws-cli-docsinstead. - General IAM policy language. Use
aws-iam-docsfor IAM fundamentals; use EKS docs for IRSA and access entries. - ECS or Lambda deployment patterns. Use
aws-ecs-docsoraws-lambda-docsinstead. - Helm chart authoring unless the question is about EKS add-ons or documented EKS integration paths.
Workflow
1. Classify the request
Decide which bucket the question belongs to before searching:
- Getting started and cluster creation
- Compute: node groups, Fargate, and Auto Mode
- Networking and load balancing
- Security, IAM, and access control
- Storage and persistent volumes
- Add-ons and platform components
- Observability and logging
- Upgrades and version lifecycle
- EKS Capabilities and integrations
- Hybrid, Anywhere, and advanced topologies
- Troubleshooting and known issues
What ships with it
2 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.
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.
- 1mo ago First seen · 114 lines · 96 tokens per session scan A dc8100f974af
aws-eks-docs is a skill published in the GitHub repository cookieMonsterDev/agents-skills (6 stars, last pushed today), licensed MIT. It adds 96 tokens to every session and 1,402 once invoked, about $0.0004 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-08-31.
Other skills, from other repositories
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
application-integration-authoring
Builds, versions, publishes, tests, and executes Google Cloud Application Integration workflows through the REST API and Python discovery client, and promotes versions across environments. Use when listing integrations, downloading or uploading integration versions as JSON, configuring API triggers or config…
gke-alert-configuration
Configures alerting policies in Terraform for Google Kubernetes Engine (GKE) clusters, workloads, and services using PromQL and Google Cloud Managed Service for Prometheus. Use when writing, analyzing, validating, or deploying Terraform alerting policies to monitor GKE service latency, traffic, error rates using…
gke-ai-troubleshooting-tpu-partition-overlap
Diagnose and resolve GKE TPU slice creation failures (SliceCreationFailed) caused by partition overlap conflicts where requested TPU partitions or their nodes are already used by another slice or JobSet. Use when diagnosing GKE TPU slice creation failures with SliceCreationFailed partition or node conflicts. Don't use…
application-integration-basics
Explains Google Cloud Application Integration concepts, region provisioning, IAM roles, run-as service accounts, interface choices (REST, Python discovery client, Terraform, ADK), and platform limits. Use when setting up Application Integration in a Google Cloud project, enabling required APIs, provisioning a region…