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-certsnpx skills add yindia/rootcause --skill k8s-certsgit 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-certs)<a href="https://agentmods.dev/skills/yindia/rootcause/k8s-certs"><img src="https://agentmods.dev/badge/skills/yindia/rootcause/k8s-certs.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.01603 |
| Opus 5 | $0.00000 | $0.00801 |
| Sonnet 5 | $0.00000 | $0.00321 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
k8s-certs 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 — 269 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: k8s-certs
Comprehensive cert-manager diagnostics for certificate lifecycle, issuer health, renewal failures, and ingress TLS integration.
Trigger Phrases
Use this skill when the user mentions:
- cert-manager broken
- certificate not ready
- tls secret missing
- x509 expired or unknown authority
- renewal failed
- letsencrypt challenge failed
- clusterissuer not ready
- ingress tls handshake error
- certificate request stuck
RootCause Tools Allowed
Only use these tool names in this skill:
k8s.cert_manager_detectk8s.diagnose_cert_managerk8s.describek8s.listk8s.eventsk8s.events_timeline
Cert-Manager Workflow Overview
Canonical path:
- detect installation
- diagnose control-plane and resource status
- inspect failing certificate and issuer
- validate event timeline for renewal attempt
- map to ingress/secret consumption impact
Certificate Lifecycle Reference
Lifecycle checkpoints:
Certificateresource created.CertificateRequestgenerated.- Issuer signs request.
- Secret populated/updated.
- Workloads consume updated secret.
- Renewal happens before expiry window.
Common lifecycle states:
- Ready true
- Ready false (temporary)
- Ready false (terminal misconfig)
Issuer Types
Let's Encrypt (ACME)
Typical dependencies:
- valid account registration
- challenge solver (HTTP-01 or DNS-01)
- ingress/dns routing correctness
Failure hotspots:
- challenge path not reachable
- DNS mismatch for hostname
- rate limits from ACME provider
Self-signed
Use cases:
- internal service encryption
- development/test clusters
Failure hotspots:
- trust chain not distributed to clients
- accidental production usage without trust setup
CA-backed internal issuer
Use cases:
- private PKI integration
- enterprise trust chains
Failure hotspots:
- missing or invalid CA secret
- expired intermediate CA
Detection and Baseline
Step 1: Confirm cert-manager footprint
Use k8s.cert_manager_detect first.
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 · 269 lines · 0 tokens per session scan A 575749b9eab6
k8s-certs 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,603 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.