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/nevaberry/nevaberry-plugins/cert-manager-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill cert-manager-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWhat 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.00009 | $0.01552 |
| Opus 5 | $0.00005 | $0.00776 |
| Sonnet 5 | $0.00002 | $0.00310 |
| Haiku 4.5 | $0.00001 | $0.00155 |
Grade A, and why
cert-manager-knowledge-patch 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 3d 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 — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
cert-manager Knowledge Patch
When to use
Load this skill for cert-manager work involving upgrades, Certificate behavior, ACME solvers, issuers, Gateway or Ingress integration, Helm configuration, metrics, RBAC, or platform compatibility.
First establish the installed cert-manager patch release, chart values, Kubernetes or OpenShift version, enabled feature gates, and relevant issuer and Certificate manifests. Patch-level fixes matter: do not assume every patch in a minor line has the same behavior.
Reference index
| Reference | Topics |
|---|---|
| Upgrades and support | Upgrade defaults, removals, required patch releases, support and platform policy |
| Certificates and issuance | Certificate fields, renewal, keystores, validation, output, reconciliation |
| ACME and DNS solvers | HTTP-01, DNS-01, profiles, solver configuration, retry behavior |
| Gateway, Ingress, and shim | ListenerSet, Gateway listeners, generated Certificates, annotations |
| Helm, operations, and security | Chart values, Pod settings, NetworkPolicy, RBAC, namespace scope |
| Issuers, integrations, and API clients | Vault, Venafi, cainjector, issuer APIs, apply clients |
| Observability and reliability | Metrics, logging, backoff, recovery, diagnostics |
Upgrade first: behavior changes and removals
Preserve private keys explicitly when required
The default Certificate.spec.privateKey.rotationPolicy is Always. Before an
upgrade, set Never on Certificates that must retain their existing key:
spec:
privateKey:
rotationPolicy: Never
The feature gate that once disabled the Always default is no longer
configurable. Per-Certificate policy is the supported control.
What ships with it
8 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.
- coverage.json 1.4 KB
- references/acme-and-dns-solvers.md 3.5 KB
- references/certificates-and-issuance.md 4.5 KB
- references/gateway-ingress-and-shim.md 2.1 KB
- references/helm-operations-and-security.md 3.5 KB
- references/issuers-integrations-and-api.md 2.7 KB
- references/observability-and-reliability.md 2.6 KB
- references/upgrades-and-support.md 4.4 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.
- 3d ago First seen · 194 lines · 9 tokens per session scan A 11d24357323e
cert-manager-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 6d ago), licensed MIT. It adds 9 tokens to every session and 1,552 once invoked, about $0.0000 per session on Opus 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-08-30.
Other skills, from other repositories
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.
infrastructure-planning
Plan and document the required software, infrastructure, and logistics for a Paperclip company — domains, GitHub, Docker Hub, Kubernetes, Slack, Google Workspace, Stripe, shipping providers, and CI/CD pipelines. Use when setting up infrastructure for a new company or auditing what an existing company needs.
kubernetes
Kubernetes and GKE operations: kubectl, manifests, deployments, services, workload identity, autopilot, config connector, private clusters, and troubleshooting.
istio
Istio service mesh: traffic management, gateways, virtual services, destination rules, mTLS, authorization policies, EnvoyFilters, and observability.
terraform
Terraform infrastructure-as-code for provisioning cloud and Kubernetes resources: modules, state and backends, providers, and plan/apply workflows.
auth
Authentication/authorization infra with Keycloak and OAuth2-proxy. Use for identity providers, SSO, OIDC/SAML, realm/client config, user federation, and OAuth2-proxy sidecar or ingress auth on Kubernetes.