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/itechmeat/llm-code/k8s-cluster-apinpx skills add itechmeat/llm-code --skill k8s-cluster-apigit clone --depth 1 https://github.com/itechmeat/llm-codeWhat 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.00086 | $0.02347 |
| Opus 5 | $0.00043 | $0.01174 |
| Sonnet 5 | $0.00017 | $0.00469 |
| Haiku 4.5 | $0.00009 | $0.00235 |
Grade B, and why
k8s-cluster-api scanned grade B with 2 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 2d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
sudo mv clusterctl /usr/local/bin/ Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -L https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.12.0/clusterctl-linux-amd64 -o clusterctl How it starts
The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Cluster API
Kubernetes Cluster API (CAPI) is a Kubernetes sub-project focused on providing declarative APIs and tooling to simplify provisioning, upgrading, and operating multiple Kubernetes clusters.
Overview
Started by SIG Cluster Lifecycle, Cluster API uses Kubernetes-style APIs and patterns to automate cluster lifecycle management. The infrastructure (VMs, networks, load balancers, VPCs) and Kubernetes configuration are defined declaratively, enabling consistent and repeatable cluster deployments across environments.
Why Cluster API?
While kubeadm reduces installation complexity, it doesn't address day-to-day cluster management:
- How to consistently provision infrastructure across providers and locations?
- How to automate cluster lifecycle (upgrades, deletion)?
- How to scale processes to manage any number of clusters?
Cluster API addresses these gaps with declarative, Kubernetes-style APIs that automate cluster creation, configuration, and management.
Goals
- Manage lifecycle (create, scale, upgrade, destroy) of Kubernetes-conformant clusters via declarative API
- Work in different environments (on-premises and cloud)
- Define common operations with swappable implementations
- Reuse existing ecosystem components (cluster-autoscaler, node-problem-detector)
- Provide transition path for existing tools to adopt incrementally
Non-Goals
- Add APIs to Kubernetes core
- Manage infrastructure unrelated to Kubernetes clusters
- Force all lifecycle products to use these APIs
- Manage non-CAPI provisioned clusters
- Manage single cluster spanning multiple providers
- Configure machines after create/upgrade
Quick Navigation
| Topic | Reference |
|---|---|
| Getting Started | getting-started.md |
| Concepts & Architecture | concepts.md |
| Certificates | certificates.md |
| Bootstrap (Kubeadm/MicroK8s) | bootstrap.md |
| Cluster Operations | cluster-operations.md |
| Experimental Features | experimental.md |
| clusterctl CLI | clusterctl.md |
| Developer Guide | developer.md |
| Troubleshooting | troubleshooting.md |
| API Reference & Providers | api-reference.md |
| Security & PSS | security.md |
| Controllers | controllers.md |
| Version Migrations | migrations.md |
| FAQ | faq.md |
| Best Practices | best-practices.md |
What ships with it
49 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.
- assets/argocd-cluster-app.yaml 4.9 KB
- assets/aws-credentials.yaml 3.9 KB
- assets/azure-credentials.yaml 4.2 KB
- assets/cluster-clusterclass.yaml 2.6 KB
- assets/cluster-minimal.yaml 3.2 KB
- assets/cluster-production.yaml 5.7 KB
- assets/clusterclass-example.yaml 6.3 KB
- assets/docker-quickstart.yaml 1.9 KB
- assets/dr-backup-restore.md 6.5 KB
- assets/etcd-backup.yaml 9.8 KB
- assets/flux-kustomization.yaml 4.3 KB
- assets/gitops-rbac.yaml 5.6 KB
- assets/migration-v1beta2.md 6.3 KB
- assets/prometheus-alerts.yaml 13 KB
- assets/provider-matrix.md 4.3 KB
- assets/security-audit-report.md 7.5 KB
- assets/troubleshooting-flow.md 10 KB
- assets/upgrade-checklist.md 4.5 KB
- references/api-reference.md 9.4 KB
- references/best-practices.md 7.5 KB
- references/bootstrap.md 8.1 KB
- references/certificates.md 3.7 KB
- references/cluster-operations.md 16 KB
- references/clusterctl.md 9.7 KB
- references/concepts.md 9.7 KB
- references/controllers.md 5.2 KB
- references/developer.md 19 KB
- references/experimental.md 9.4 KB
- references/faq.md 6.6 KB
- references/getting-started.md 11 KB
- references/migrations.md 8.9 KB
- references/security.md 8.0 KB
- references/troubleshooting.md 6.4 KB
- scripts/analyze-conditions/main.go 7.9 KB
- scripts/audit-security/main.go 12 KB
- scripts/check-cluster-health/main.go 7.8 KB
- scripts/check-provider-contract/main.go 13 KB
- scripts/compare-versions/main.go 11 KB
- scripts/export-cluster-state/main.go 11 KB
- scripts/generate-cluster-template/main.go 15 KB
- scripts/go.mod 145 B
- scripts/go.sum 361 B
- scripts/internal/kubectl/kubectl.go 3.8 KB
- scripts/lint-cluster-templates/main.go 11 KB
- scripts/migration-checker/main.go 11 KB
- scripts/run-clusterctl-diagnose/main.go 5.5 KB
- scripts/scaffold-provider/main.go 30 KB
- scripts/timeline-events/main.go 9.3 KB
- scripts/validate-manifests/main.go 10 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.
- 2d ago First seen · 235 lines · 86 tokens per session scan B be648dd1fa31
k8s-cluster-api is a skill published in the GitHub repository itechmeat/llm-code (22 stars, last pushed 1mo ago), licensed MIT. It adds 86 tokens to every session and 2,347 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 2 findings (asks for root, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…