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/evolplus/talos/kubernetes-deploymentnpx skills add evolplus/talos --skill kubernetes-deploymentgit clone --depth 1 https://github.com/evolplus/talosWrote 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/evolplus/talos/kubernetes-deployment)<a href="https://agentmods.dev/skills/evolplus/talos/kubernetes-deployment"><img src="https://agentmods.dev/badge/skills/evolplus/talos/kubernetes-deployment.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.00071 | $0.01096 |
| Opus 5 | $0.00036 | $0.00548 |
| Sonnet 5 | $0.00014 | $0.00219 |
| Haiku 4.5 | $0.00007 | $0.00110 |
Grade C, and why
kubernetes-deployment scanned grade C with 1 finding 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.
Reaches for credential fileshighPrivilege escalation
SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.
- Never read or print kubeconfig files, `.k8s/*config*`, `.kube/config`, service-account tokens, client key data, or Kubernetes Secret manifests. How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Deployment
When to use
Use this skill when a DevOps task deploys or verifies services on a Kubernetes cluster. Project-root .k8s/ may contain manifests, overlays, or kubeconfig files. Kubeconfig and Secret material are operator-owned credentials: DevOps may reference them in kubectl or helm commands, but must not read, summarize, copy, or print their contents.
Inputs and outputs
- Inputs: task ID, target environment, cluster/context/namespace, approved kubeconfig path or context, manifest/Kustomize/Helm path, image tag, environment contract, rollout and rollback expectations.
- Outputs: dry-run/diff evidence, applied resource summary, rollout status, service endpoint/health evidence, rollback command, and
docs/deploy-reports/<task-id>.mdwith credential material redacted.
Procedure
-
Resolve cluster, namespace, and kubeconfig by reference. Use explicit
--kubeconfig <path>and--namespace <name>or an approved context from the task. Do not rely on an implicit current context. Do not runkubectl config view, especially with--raw. -
Separate manifests from secrets. It is safe to read ordinary Deployment, Service, Ingress, ConfigMap, HPA, and Kustomize/Helm metadata. Do not read kubeconfig files, Kubernetes Secret manifests, sealed-secret private keys, service-account tokens, or files whose path implies secret material.
-
Validate before mutation. Run schema or server dry-run validation first:
kubectl --kubeconfig .k8s/<config> --namespace <ns> apply --dry-run=server -f <manifest-or-overlay> kubectl --kubeconfig .k8s/<config> --namespace <ns> diff -f <manifest-or-overlay>If diff output contains secret values, stop and rerun with safer tooling or ask the operator for a redacted plan.
-
Use explicit image and config inputs. Apply manifests or Helm values that reference immutable image tags/digests. Non-secret ConfigMaps may be reviewed. Secrets must come from the cluster's approved secret manager, ExternalSecret, sealed-secret public workflow, or operator-managed injection path.
-
Deploy with bounded blast radius. Apply only the task-scoped namespace/resources. Avoid cluster-wide operations unless the task is explicitly a platform task with approval. Never run
kubectl deleteagainst broad selectors without a reviewed manifest list. -
Watch rollouts. Use
kubectl rollout status deployment/<name> --timeout=<n>s, pod readiness, service endpoints, and application health checks. Capture only resource names, statuses, events, and sanitized logs. -
Prepare rollback. Record
kubectl rollout undo, Helm rollback revision, or re-apply previous manifest/tag. For database migrations or irreversible changes, route back to SA/TL before production deployment. -
Write the deploy report. Include cluster alias/context name, namespace, manifest path, image tag/digest, validation/diff result, rollout status, health evidence, and rollback command. Never include kubeconfig contents, tokens, cert data, or Secret values.
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 · 58 lines · 71 tokens per session scan C 7121bdf60152
kubernetes-deployment is a skill published in the GitHub repository evolplus/talos (8 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 71 tokens to every session and 1,096 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it C with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…