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 skills add sigistry/marketplace --skill k8s-manifest-validationgit clone --depth 1 https://github.com/sigistry/marketplaceWrote 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/sigistry/marketplace/k8s-manifest-validation)<a href="https://agentmods.dev/skills/sigistry/marketplace/k8s-manifest-validation"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/k8s-manifest-validation/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/skills/sigistry/marketplace/k8s-manifest-validation"><img src="https://agentmods.dev/badge/skills/sigistry/marketplace/k8s-manifest-validation.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.00084 | $0.00783 |
| Opus 5 | $0.00042 | $0.00392 |
| Sonnet 5 | $0.00017 | $0.00157 |
| Haiku 4.5 | $0.00008 | $0.00078 |
Grade B, and why
k8s-manifest-validation scanned grade B 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 11d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
`kubectl apply` validates schema, not intent. A manifest can apply cleanly and then: never pass readiness, get OOMKilled, run as root against policy, or route traffic to a dead Pod. Static pre-flight catches these before How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Manifest Validation
Purpose
A consistent pre-deploy checklist for the Kubernetes manifest mistakes that pass kubectl apply but never become Ready, silent failures. This is K8s-specific domain knowledge about how manifests fail quietly, not generic YAML linting.
The silent-failure principle
kubectl apply validates schema, not intent. A manifest can apply cleanly and then: never pass readiness, get OOMKilled, run as root against policy, or route traffic to a dead Pod. Static pre-flight catches these before they reach the cluster.
Validation checklist (assign PASS / WARN / FAIL)
| Check | FAIL condition | Why it fails silently |
|---|---|---|
| Type / quoting | containerPort: "8080" (string), "true" bool, int env value |
schema accepts strings; port never binds / value mis-typed |
| Resource requests & limits | missing on a container | BestEffort QoS → first evicted; can starve the node |
| Readiness probe | missing | traffic routed before the app can serve → 502s |
| Liveness probe | missing (WARN) or too aggressive (FAIL) | wedged Pod never restarts; or healthy Pod killed in a loop |
| Startup probe | missing on slow-starting app | liveness kills it before it finishes booting |
| securityContext | runAsNonRoot unset, caps not dropped, writable rootfs |
runs as root; policy admission may reject later |
| Image tag | :latest or untagged |
non-reproducible; rollout pulls a different image silently |
| Replicas / PDB | single replica, no PodDisruptionBudget | node drain / rollout causes full downtime |
| Hardcoded secrets | literal token/password in env or ConfigMap | secret committed to git; ConfigMaps aren't secret |
| Namespace | relies on implicit default |
deploys to the wrong place; RBAC/quota surprises |
Type-quoting quick rules
containerPort,port,targetPort(numeric),replicas→ integers, unquoted.- Boolean fields (
runAsNonRoot,readOnlyRootFilesystem) → baretrue/false, never"true". - Env
value:is always a string: wrap numbers/bools in quotes:value: "5432". - YAML gotcha: unquoted
on,off,yes,no, and1.20get coerced, quote version strings.
What ships with it
2 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.
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.
- 11d ago First seen · 45 lines · 84 tokens per session scan B b3fc653f55ab
k8s-manifest-validation is a skill published in the GitHub repository sigistry/marketplace (3 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 783 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
helm
Helm chart authoring, templating, and release management for Kubernetes: charts, values, templating functions, repositories, dependencies, and lifecycle operations.
deploy-mcp
Deploy the FutureSearch MCP server to staging or production on GKE. Use when the user wants to deploy, redeploy, roll back, scale replicas, or check deployment status. Triggers on deploy, redeploy, staging, production, rollout, scale, replicas.
infrastructure-validation
Use when working with Terraform (.tf, .tfvars), Ansible (playbooks, roles, inventory), Docker (Dockerfile, docker-compose.yml), Kubernetes (manifests, Helm charts), CloudFormation, or any infrastructure-as-code files. Also use when running terraform plan/apply, building Docker images, writing Helm templates, or when…
companion-clis
Companion CLIs for Runpod workflows — HuggingFace, GitHub, Docker, and AWS.
vllm-deployment
Use this skill when authoring, reviewing, or fixing a vLLM Kubernetes manifest, Docker/Podman pod, or OpenShift ServingRuntime — even when the user does not say "vllm". Triggers on: lab cluster performance practices, cache mount + survival across pod restarts (/root/.cache, VLLMCACHEROOT, TORCHINDUCTORCACHEDIR…
infra-standards
Infrastructure, container, and CI/CD discipline — IaC, Dockerfiles and compose files, CI pipelines, platform deploy config, env/secrets handling. INVOKE PROACTIVELY when creating or editing any such file (.tf, .bicep, Dockerfile, docker-compose, .github/workflows/, vercel.json) — even when nobody says "infra". Not for…