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/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/commands/sigistry/marketplace/k8s-preflight)<a href="https://agentmods.dev/commands/sigistry/marketplace/k8s-preflight"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/k8s-preflight/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/commands/sigistry/marketplace/k8s-preflight"><img src="https://agentmods.dev/badge/commands/sigistry/marketplace/k8s-preflight.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.00014 | $0.00696 |
| Opus 5 | $0.00007 | $0.00348 |
| Sonnet 5 | $0.00003 | $0.00139 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
k8s-preflight 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 10d 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-flight Kubernetes manifests before they reach the cluster, catching the silent failures that pass kubectl apply but never become Ready. Use this before every deploy or in a CI gate. $ARGUMENTS is a manifest file or a directory to scan; default to the current directory's *.yaml/*.yml and any k8s/, manifests/, or deploy/ folder.
Process
Step 1: Collect the manifests
- Read the file or glob the directory in
$ARGUMENTSfor*.yaml/*.yml. - Split multi-document files on
---. For each document, recordkind,metadata.name, andmetadata.namespace. - If Helm templates or
values.yamlare present, note that values may inject the fields you are checking, flag unresolved{{ ... }}rather than treating them as literals.
Step 2: Validate against the checklist
Apply the k8s-manifest-validation skill. Run each check and assign a gate result:
| Check | FAIL when | Skill reference |
|---|---|---|
| Type / quoting | port is a quoted string, boolean quoted as "true", env value is an int |
manifest-checklist.md |
| Resource requests & limits | missing on any container | probes-and-resources.md |
| Liveness / readiness / startup probes | readiness missing (WARN if only startup missing) | probes-and-resources.md |
securityContext |
runAsNonRoot unset, no dropped capabilities, writable root fs |
probes-and-resources.md |
| Image tag | :latest or untagged |
manifest-checklist.md |
| Replicas / PodDisruptionBudget | single replica for a stateless Deployment, no PDB | manifest-checklist.md |
| Hardcoded secrets | literal tokens/passwords in env or ConfigMap | manifest-checklist.md |
| Namespace | relies on implicit default |
manifest-checklist.md |
Step 3: Report as a gate
Emit a gated checklist: one row per check per workload:
| Check | Resource (kind/name) |
Result | Detail (file:line) |
|---|
Use PASS / WARN / FAIL. Then, for every FAIL and WARN, provide the corrected YAML snippet. End with an overall verdict line: GATE: PASS only if there are zero FAILs, otherwise GATE: FAIL.
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.
- 10d ago First seen · 43 lines · 14 tokens per session scan A 3f5693efa09d
k8s-preflight is a command published in the GitHub repository sigistry/marketplace (3 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 696 once invoked, about $0.0001 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-31.
Other commands, from other repositories
dockcleanbuild
Clean Docker environment and rebuild all images and containers from scratch.
dockbuild
Quick Docker Compose build and start with full output.
typescript-dev
Start TypeScript development workflow with architecture, implementation, review, and testing phases.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
compliance-fix
Show Qualimetry review findings for a file and apply the standards-compliant fix.
fr-isolation
Run work in an isolated workspace: git worktree + devcontainer, driven through the fr isolation CLI (exec-bridge). Use when feature work must not touch the base repo, when fr-brainstorming or fr-goal needs a workspace, when the operator says "isolate this" / "run it in the container", or to clean up after a merged PR.…