Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/kinhluan/rules-quarkus-skillsnpx agentmods add skills/kinhluan/rules-quarkus-skills/bazel-k8s-expertWrote 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/kinhluan/rules-quarkus-skills/bazel-k8s-expert)<a href="https://agentmods.dev/skills/kinhluan/rules-quarkus-skills/bazel-k8s-expert"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/bazel-k8s-expert/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/kinhluan/rules-quarkus-skills/bazel-k8s-expert"><img src="https://agentmods.dev/badge/skills/kinhluan/rules-quarkus-skills/bazel-k8s-expert.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.00045 | $0.03748 |
| Opus 5 | $0.00023 | $0.01874 |
| Sonnet 5 | $0.00009 | $0.00750 |
| Haiku 4.5 | $0.00005 | $0.00375 |
Grade A, and why
bazel-k8s-expert 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 12d 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 — 673 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bazel-k8s-expert
Keyword: k8s | Platforms: gemini,claude,codex
Bazel Kubernetes Expert Skill - Deploying, managing, and operating Quarkus and Java applications on Kubernetes using Bazel-native tooling.
Core Mandates
- GitOps-Ready: All K8s manifests must be generated from Bazel targets, never hand-edited YAML in production.
- Hermetic Deployments: Use
rules_k8sorhelmvia Bazel to ensure deployment artifacts match built images exactly. - Health Probes: Every deployment must define
@Livenessand@Readinessprobes (seemicroprofile-expert). - Resource Limits: Always set CPU/memory requests and limits to prevent cluster starvation.
- Config Externalization: Use ConfigMaps and Secrets for environment-specific values; never bake config into images.
Setup (Bzlmod)
MODULE.bazel
bazel_dep(name = "rules_k8s", version = "0.7")
bazel_dep(name = "rules_helm", version = "0.1")
# For Kustomize support
bazel_dep(name = "rules_kustomize", version = "0.1")
rules_k8s Deployment
Basic Deployment + Service
# services/user/k8s/BUILD.bazel
load("@rules_k8s//k8s:defs.bzl", "k8s_deploy")
k8s_deploy(
name = "user-service_deploy",
template = ":deployment.yaml",
images = {
"user-service": "//services/user:user-service_image",
},
)
# services/user/k8s/deployment.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: user-service
labels:
app: user-service
spec:
replicas: 3
selector:
matchLabels:
app: user-service
template:
metadata:
labels:
app: user-service
spec:
containers:
- name: user-service
image: user-service # Replaced by rules_k8s
ports:
- containerPort: 8080
env:
- name: QUARKUS_HTTP_PORT
value: "8080"
- name: JAVA_TOOL_OPTIONS
value: "-XX:+UseContainerSupport -XX:MaxRAMPercentage=75.0"
resources:
requests:
memory: "256Mi"
cpu: "250m"
limits:
memory: "512Mi"
cpu: "500m"
livenessProbe:
httpGet:
path: /q/health/live
port: 8080
initialDelaySeconds: 30
periodSeconds: 10
readinessProbe:
httpGet:
path: /q/health/ready
port: 8080
initialDelaySeconds: 5
periodSeconds: 5
---
apiVersion: v1
kind: Service
metadata:
name: user-service
spec:
selector:
app: user-service
ports:
- port: 80
targetPort: 8080
type: ClusterIP
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.
- 12d ago First seen · 673 lines · 45 tokens per session scan A 69ad9258d709
bazel-k8s-expert is a skill published in the GitHub repository kinhluan/rules-quarkus-skills (3 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 3,748 once invoked, about $0.0002 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 skills, from other repositories
kubernetes-docs
Kubernetes 1.36 — Pods, Deployments, Services, Ingress, ConfigMaps, Secrets, RBAC, CRDs, Operators, kubectl, Helm.
k8s-deployer
Kubernetes deployment management - generate manifests, Helm charts, manage rollouts, check cluster status, and apply security best practices.
kubernetes-operator
Deploy and manage applications on Kubernetes. Covers deployments, services, ingress, HPA, secrets, and production-grade cluster configuration.
kubernetes
Kubernetes operations playbook for deploying services: core objects, probes, resource sizing, safe rollouts, and fast kubectl debugging.
container-manager-kubernetes-operations
Full operational Kubernetes surface via the container-manager-mcp MCP server — workloads (pods/rollouts/StatefulSets/DaemonSets/ReplicaSets/Jobs/CronJobs), config (ConfigMaps/Secrets/Namespaces/CRDs/patch), networking (Ingress/native Services/NetworkPolicy/DNS), storage (PV/PVC/StorageClass/snapshots/CSI), RBAC…
kubernetes
Kubernetes orchestration authority — pods, deployments, services, ingress, helm charts, kustomize overlays, RBAC, network policies, operators, StatefulSets for databases, production-grade cluster hardening, and kubectl workflows.