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/HermeticOrmus/LibreSecOps-Claude-CodeWrote 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/hermeticormus/libresecops-claude-code/k8s-sec-audit)<a href="https://agentmods.dev/commands/hermeticormus/libresecops-claude-code/k8s-sec-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/k8s-sec-audit/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/hermeticormus/libresecops-claude-code/k8s-sec-audit"><img src="https://agentmods.dev/badge/commands/hermeticormus/libresecops-claude-code/k8s-sec-audit.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.00043 | $0.01256 |
| Opus 5.5 | $0.00017 | $0.00502 |
| Sonnet 5.5 | $0.00009 | $0.00251 |
| Haiku 4.5 | $0.00004 | $0.00126 |
Grade A, and why
k8s-sec-audit scanned grade A 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 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.
Unrestricted tool accesslowExcessive agency
A wildcard tool grant or "run any command" leaves no least-privilege boundary at all.
- Roles with `create` on `pods` (can run arbitrary code) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/k8s-sec-audit
Structured audit of Kubernetes cluster security configuration.
Trigger
Use when you need to:
- Assess the security posture of a Kubernetes cluster
- Review Kubernetes manifests, Helm charts, or Kustomize overlays before deployment
- Prepare for a CIS Kubernetes Benchmark assessment
- Evaluate a managed Kubernetes service (EKS, GKE, AKS) configuration
- Investigate cluster security after an incident or organizational change
Input
One of:
- Live cluster:
kubectlaccess (preferably cluster-admin for comprehensive audit, or view-only for least-privilege assessment) - Manifests: Kubernetes YAML files, Helm charts, Kustomize overlays
- kube-bench output: Previous CIS Benchmark scan results
- Specific scope: Focus area (e.g., "RBAC", "network policies", "workload security")
Process
Phase 1: Control Plane
-
API server configuration
- Authentication methods (
kubectl cluster-info, OIDC configuration) - Anonymous authentication disabled
- API server accessible from internet? (EKS:
--api-server-endpoint-access) - Audit logging enabled and configured
- Authentication methods (
-
Admission controllers
- Pod Security Admission labels on namespaces (
kubectl get ns -o yaml) - Additional admission controllers (Gatekeeper, Kyverno, OPA)
- Webhook configurations (
kubectl get validatingwebhookconfigurations)
- Pod Security Admission labels on namespaces (
-
etcd security
- Encryption at rest enabled (
kubectl get secrets -n kube-systemfor EncryptionConfiguration) - etcd access restricted (self-managed clusters)
- Encryption at rest enabled (
Phase 2: RBAC
-
ClusterRoleBindings
kubectl get clusterrolebindings -o json | jq '.items[] | select(.roleRef.name == "cluster-admin") | .subjects'cluster-adminbindings (should be minimal)- System:masters group membership
- Anonymous user bindings
-
Dangerous permissions
- Roles with
createonpods(can run arbitrary code) - Roles with
createonpods/exec(can exec into existing pods) - Roles with
*on all resources - Roles with access to secrets across namespaces
- Service accounts with excessive permissions
- Roles with
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 Changed · +5 lines · +43 tokens per session 5703d13b1b92
- 1mo ago First seen · 151 lines · 0 tokens per session scan A a40131e5af29
k8s-sec-audit is a command published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 43 tokens to every session and 1,256 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (unrestricted tool access). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.