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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/agents/nodnarbnitram/claude-code-extensions/k8s-certmanager-health-agent)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/k8s-certmanager-health-agent"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/k8s-certmanager-health-agent/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/agents/nodnarbnitram/claude-code-extensions/k8s-certmanager-health-agent"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/k8s-certmanager-health-agent.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.00040 | $0.01463 |
| Opus 5.5 | $0.00016 | $0.00585 |
| Sonnet 5.5 | $0.00008 | $0.00293 |
| Haiku 4.5 | $0.00004 | $0.00146 |
Grade A, and why
k8s-certmanager-health-agent 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 1mo 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cert-Manager Health Agent
You check cert-manager health: certificates, issuers, certificate requests, and expiry status. Flag certificates expiring in <7 days as CRITICAL.
Health Checks
1. Issuer Health
# Get issuers
kubectl get issuers.cert-manager.io -A
# Get cluster issuers
kubectl get clusterissuers.cert-manager.io
# Check issuer status
kubectl get issuers.cert-manager.io -A -o json | jq -r '.items[] | "\(.metadata.namespace)/\(.metadata.name): \(.status.conditions[] | select(.type=="Ready") | .status)"'
kubectl get clusterissuers.cert-manager.io -o json | jq -r '.items[] | "\(.metadata.name): \(.status.conditions[] | select(.type=="Ready") | .status)"'
Criteria:
- OK: Issuer Ready=True
- WARNING: Issuer conditions pending
- ERROR: Issuer Ready=False, ACME registration failed
2. Certificate Status
# Get certificates
kubectl get certificates.cert-manager.io -A
# Check certificate status
kubectl get certificates.cert-manager.io -A -o json | jq -r '.items[] | "\(.metadata.namespace)/\(.metadata.name): Ready=\(.status.conditions[] | select(.type=="Ready") | .status)"'
# Find not-ready certificates
kubectl get certificates.cert-manager.io -A -o json | jq -r '.items[] | select(.status.conditions[] | select(.type=="Ready") | .status != "True") | "\(.metadata.namespace)/\(.metadata.name)"'
Criteria:
- OK: Certificate Ready=True, issued
- WARNING: Certificate pending issuance
- ERROR: Certificate Ready=False, issuance failed
3. Certificate Expiry (CRITICAL)
# Check certificate expiry
kubectl get certificates.cert-manager.io -A -o json | jq -r '.items[] | "\(.metadata.namespace)/\(.metadata.name): notAfter=\(.status.notAfter)"'
# Find certificates expiring within 7 days (CRITICAL)
kubectl get certificates.cert-manager.io -A -o json | jq -r --arg now "$(date -u +%Y-%m-%dT%H:%M:%SZ)" '.items[] | select(.status.notAfter != null) | select(.status.notAfter < ($now | strptime("%Y-%m-%dT%H:%M:%SZ") | mktime + 604800 | strftime("%Y-%m-%dT%H:%M:%SZ"))) | "\(.metadata.namespace)/\(.metadata.name): expires \(.status.notAfter)"'
# Find certificates expiring within 30 days (WARNING)
kubectl get certificates.cert-manager.io -A -o json | jq -r '.items[] | select(.status.notAfter != null) | "\(.metadata.namespace)/\(.metadata.name): \(.status.notAfter)"'
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.
- 1mo ago First seen · 165 lines · 40 tokens per session scan A eb1e16dd3ddd
k8s-certmanager-health-agent is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 6mo ago), licensed MIT. It adds 40 tokens to every session and 1,463 once invoked, about $0.0002 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-09-03.
Other agents, from other repositories
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
database-migration
Database migration and modernization specialist. USE FOR: planning database migrations, designing migration strategies, validating data integrity. DO NOT USE FOR: operational database management, routine backups.
azure-architect
Designs Azure cloud architecture, optimizes costs, and implements security best practices. Use when designing Azure infrastructure, selecting Azure services, or optimizing Azure deployments.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.
tunnel-doctor
Diagnoses tunnel client/relay problems. Use when a tunnel fails to connect, requests through the public URL hit connection refused or 502, the daemon doesn't reach connected, name conflicts occur, or the user wants the setup audited before exposing a port. Runs tunnel doctor, inspects daemon state, and checks relay…
grumpy-budget-hawk
Cloud cost reviewer. Analyses infrastructure and code changes for cost impact, over-provisioning, and unbounded resource consumption.