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 nitinjain999/platform-skills --skill karpentergit clone --depth 1 https://github.com/nitinjain999/platform-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/nitinjain999/platform-skills/karpenter)<a href="https://agentmods.dev/skills/nitinjain999/platform-skills/karpenter"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/karpenter/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/nitinjain999/platform-skills/karpenter"><img src="https://agentmods.dev/badge/skills/nitinjain999/platform-skills/karpenter.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.00131 | $0.06211 |
| Opus 5.5 | $0.00052 | $0.02484 |
| Sonnet 5.5 | $0.00026 | $0.01242 |
| Haiku 4.5 | $0.00013 | $0.00621 |
Grade A, and why
karpenter 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 5d 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 — 501 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design, install, debug, review, plan capacity, audit, migrate, and upgrade Karpenter on EKS.
Verify current stable version before installing (Karpenter uses OCI, not a Helm repo):
crane ls public.ecr.aws/karpenter/karpenter | grep -E '^[0-9]+.[0-9]+.[0-9]+$' | sort -V | tail -5
Pin to the version from that output, e.g.:
helm upgrade --install karpenter oci://public.ecr.aws/karpenter/karpenter --version x.y.z
All guidance targets the karpenter.sh/v1 API. The v0.x Provisioner/AWSNodeTemplate API was removed in v1.0 — if you are on v0.x, use migrate mode first.
Interactive Wizard (fires when no arguments are provided)
When invoked with no arguments, ask before proceeding:
Q1 — Mode?
What do you need?
1. generate — design NodePool and EC2NodeClass from requirements
2. debug — diagnose why nodes are not provisioning or pods are stuck Pending
3. review — production-readiness review of existing NodePool/EC2NodeClass
4. audit — reconstruct scale-out/scale-in history and explain why it happened
5. plan — predict what Karpenter would provision for a given workload before deploying
6. migrate — move from Cluster Autoscaler to Karpenter
7. upgrade — upgrade Karpenter version (including v0.x → v1.x CRD migration)
Enter 1–7 or mode name:
Q2 — Environment context (ask after mode, one question at a time):
1. EKS cluster version? (e.g. 1.29, 1.30, 1.31)
2. Karpenter version currently installed (or target version for fresh install)?
3. Identity method for Karpenter controller?
a) EKS Pod Identity (recommended, requires EKS 1.24+)
b) IRSA (IAM Roles for Service Accounts)
4. Is this a private cluster (no public API endpoint)? [yes/no]
5. Do you use Spot instances? [yes / no / mixed]
6. Are you migrating from Cluster Autoscaler? [yes/no]
Use the answers to set defaults for every section below. If the user pastes a manifest or error, infer as much as possible and skip questions already answered.
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.
- 5d ago First seen · 501 lines · 131 tokens per session scan A a7b193866038
karpenter is a skill published in the GitHub repository nitinjain999/platform-skills (70 stars, last pushed 3d ago), licensed Apache-2.0. It adds 131 tokens to every session and 6,211 once invoked, about $0.0005 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-12.
Other skills, from other repositories
brewpage-publish
Publish HTML, markdown, text, any file, or a multi-file site to brewpage.app — free hosting with no sign-up. Paste text, share a file, upload a site, or host a temporary page and get an instant public URL to share a link. Asks namespace and password, returns the public URL. Triggers: publish, publish HTML, share link…
terraform
Terraform and OpenTofu configuration, modules, testing, state management, and HCL review. Use for "terraform module", "terraform test", "infrastructure as code", "IaC", "HCL", "tfvars", "terraform plan", "terraform apply", "OpenTofu", "tftest", or multi-environment patterns.
health-check-endpoints
Implements liveness and readiness health check endpoints following Kubernetes probe conventions. Covers response schema, dependency checks, Kubernetes probe config, and circuit breaker integration. Invoked when the user asks to add health checks, implement a /health endpoint, or set up Kubernetes probes.
devops
Use when setting up CI/CD pipelines, deploying applications, managing cloud infrastructure (AWS, GCP, Azure), implementing monitoring, containerizing services, or automating deployments with infrastructure as code.
add-terraform-module
Scaffold a new Terraform module with variables, main, and outputs. Use when provisioning a new cloud resource (database, cache, storage, etc.) that needs its own Terraform module and optional IaC wrapper wiring.
infra-apply
Run terraform plan for review and optionally apply infrastructure changes. Use when the user wants to preview or deploy infrastructure — always shows the plan before any apply.