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/yindia/rootcause/k8s-rolloutsnpx skills add yindia/rootcause --skill k8s-rolloutsgit clone --depth 1 https://github.com/yindia/rootcauseWrote 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/yindia/rootcause/k8s-rollouts)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-rollouts"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-rollouts.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.1 | $0.00000 | $0.01672 |
| Opus 5 | $0.00000 | $0.00836 |
| Sonnet 5 | $0.00000 | $0.00334 |
| Haiku 4.5 | $0.00000 | $0.00167 |
Grade A, and why
k8s-rollouts 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 6d 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 — 291 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-rollouts
Safe rollout and rollback execution framework with explicit preflight gates, restart safety checks, and Helm rollback advisory evidence.
Trigger Phrases
Use this skill when the user mentions:
- rollout stuck
- restart deployment safely
- rollback release
- canary failed
- blue green cutover issue
- pods not updating
- new version unhealthy
- helm rollback target
RootCause Tools Allowed
Only use these tool names in this skill:
k8s.rollout(actions:statusorrestart, withconfirm=truefor restart)k8s.restart_safety_checkk8s.best_practicek8s.safe_mutation_preflightk8s.describek8s.eventshelm.rollback_advisorhelm.diff_releasehelm.status
Rollout Safety Model
Never mutate first.
Required order before restart:
k8s.restart_safety_checkk8s.best_practicek8s.safe_mutation_preflightk8s.rolloutrestart withconfirm=true
If any safety gate is red, document and remediate before restart.
Deployment Strategy Comparison
| Strategy | Strength | Risk | Best Use Case |
|---|---|---|---|
| Rolling update | simple, built-in | partial outage if probes weak | most stateless services |
| Canary | controlled exposure | more routing complexity | high-risk feature changes |
| Blue-green | fast rollback switch | duplicate capacity cost | strict availability requirements |
| Recreate | deterministic replacement | downtime window | non-critical or maintenance workloads |
This skill supports diagnostics across these strategies, even when actual controller remains Deployment/Helm based.
Safe Rollout Workflow
Step 1: Check current rollout health
Use k8s.rollout status:
action: status
kind: Deployment
name: payments-api
namespace: payments
confirm: true
Then gather warning evidence:
namespace: payments
involvedObjectKind: Deployment
involvedObjectName: payments-api
Tool: k8s.events.
Step 2: Run restart safety check
Use k8s.restart_safety_check:
namespace: payments
name: payments-api
minReadyReplicas: 2
maxUnavailableRatio: 0.25
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.
- 6d ago First seen · 291 lines · 0 tokens per session scan A 91fb9a6ee2fb
k8s-rollouts is a skill published in the GitHub repository yindia/rootcause (42 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,672 tokens. 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-30.
Other skills, from other repositories
kubernetes-review
Kubernetes & Cloud-Native Review: Reviews Kubernetes manifests, Helm charts, and cloud-native configurations for security, reliability, resource management, and best practices. Covers pods, deployments, services, ingress, RBAC, network policies, HPA, PDB, security contexts, and GitOps patterns. Use when the user…
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.
upgrade-cluster
Use when upgrading or hardening an existing kube-hetzner cluster, including module version bumps, provider lockfile refreshes, k3s/RKE2 channel/version upgrades, immutable node replacement, system-upgrade-controller changes, or live cluster rollout validation.
dependabot-batch
Use when reviewing Radar's weekly Dependabot PRs and replacing the safe, 72-hour-soaked updates with one changelog-vetted, tested PR.
test-radar
Use when building and testing Radar changes with the repository's real-instance smoke-test workflow.
visual-test
Use when visually testing Radar UI changes against a real Kubernetes cluster with Playwright screenshots.