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 HermeticOrmus/LibreSecOps-Claude-Code --skill k8s-rbac-patternsgit 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/skills/hermeticormus/libresecops-claude-code/k8s-rbac-patterns)<a href="https://agentmods.dev/skills/hermeticormus/libresecops-claude-code/k8s-rbac-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/k8s-rbac-patterns/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/hermeticormus/libresecops-claude-code/k8s-rbac-patterns"><img src="https://agentmods.dev/badge/skills/hermeticormus/libresecops-claude-code/k8s-rbac-patterns.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.00069 | $0.02783 |
| Opus 5.5 | $0.00028 | $0.01113 |
| Sonnet 5.5 | $0.00014 | $0.00557 |
| Haiku 4.5 | $0.00007 | $0.00278 |
Grade A, and why
k8s-rbac-patterns 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
K8s RBAC Patterns
RBAC design patterns, least-privilege role definitions, common misconfigurations, and privilege escalation prevention.
Knowledge Base
RBAC Object Model
Kubernetes RBAC uses four object types:
| Object | Scope | Purpose |
|---|---|---|
| Role | Namespace | Defines permissions within a single namespace |
| ClusterRole | Cluster-wide | Defines permissions across all namespaces or for cluster-scoped resources |
| RoleBinding | Namespace | Binds a Role OR ClusterRole to subjects within a namespace |
| ClusterRoleBinding | Cluster-wide | Binds a ClusterRole to subjects across all namespaces |
Critical distinction: A ClusterRole bound with a RoleBinding is scoped to that namespace. The same ClusterRole bound with a ClusterRoleBinding applies cluster-wide. This is how you create reusable role definitions with namespace-scoped grants.
RBAC Evaluation Logic
- All RBAC rules are additive -- there is no deny rule in Kubernetes RBAC
- If no rule grants access, the request is denied by default
- Rules are evaluated by the API server at request time
system:mastersgroup bypasses RBAC entirely (built into the API server)- The
escalateandbindverbs control whether a user can create roles more powerful than their own
Privilege Escalation Through RBAC
These permissions enable RBAC-based privilege escalation:
| Permission | Escalation Path |
|---|---|
create pods |
Create a pod with any service account, mounting secrets, using hostPath |
create pods/exec |
Exec into a pod running with a more-privileged service account |
create serviceaccounts + create rolebindings |
Create a SA and bind cluster-admin to it |
escalate on roles |
Create or modify roles to have more permissions than you have |
bind on roles |
Bind any role (including cluster-admin) to any subject |
impersonate |
Act as any user, group, or service account |
create secrets |
Create a service account token secret for any SA |
patch nodes |
Modify node labels to bypass scheduling constraints |
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 · +69 tokens per session d6f9470f4aa7
- 1mo ago First seen · 298 lines · 0 tokens per session scan A 214864099691
k8s-rbac-patterns is a skill published in the GitHub repository HermeticOrmus/LibreSecOps-Claude-Code (4 stars, last pushed 9d ago), licensed MIT. It adds 69 tokens to every session and 2,783 once invoked, about $0.0003 per session on Opus 5.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-09-03.
Other skills, from other repositories
implementing-devsecops-security-scanning
Integrates Static Application Security Testing (SAST), Dynamic Application Security Testing (DAST), and Software Composition Analysis (SCA) into CI/CD pipelines using open-source tools. Covers Semgrep for SAST, Trivy for SCA and container scanning, OWASP ZAP for DAST, and Gitleaks for secrets detection. Activates for…
building-devsecops-pipeline-with-gitlab-ci
Design and implement a comprehensive DevSecOps pipeline in GitLab CI/CD integrating SAST, DAST, container scanning, dependency scanning, and secret detection.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
implementing-runtime-application-self-protection
Deploy Runtime Application Self-Protection (RASP) agents to detect and block attacks from within application runtime, covering OpenRASP integration, attack pattern detection, and security policy configuration for Java and Python web applications.
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
audit-production-readiness
Audit a repository or service for release-blocking bugs, security, data/privacy, AI-agent, supply-chain, operability, and scale risks. Use for deep code audits, threat models, pre-production reviews, vulnerability triage, incidents, defensive investigation, release gates, or evidence-based 10k-to-1M-user readiness.