Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

K8s Rbac Review

ASecurity

Audit Kubernetes RBAC for least privilege and privilege-escalation paths — cluster-admin sprawl, wildcard/dangerous verbs, risky bindings, and service-account token exposure. Use to review who can do what in a cluster and find escalation to cluster-admin.

8 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsgonodekubernetesapisecurity

Works with

api

Security Analysis

A100/100

Scanned 9/19/2026

$npx -y skills add jassics/awesome-claude-security --skill k8s-rbac-review --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of K8s Rbac Review?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for K8s Rbac Review
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jassics-k8s-rbac-review/badge)](https://www.skillsdirectory.com/skills/jassics-k8s-rbac-review)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: k8s-rbac-review
description: >-
  Audit Kubernetes RBAC for least privilege and privilege-escalation paths —
  cluster-admin sprawl, wildcard/dangerous verbs, risky bindings, and service-account
  token exposure. Use to review who can do what in a cluster and find escalation to
  cluster-admin.
---

# Goal

An RBAC risk assessment: which subjects (users, groups, service accounts) hold
excessive or dangerous permissions, and which paths lead to cluster-admin — with
least-privilege fixes.

# Dangerous permissions to hunt

- **Escalation primitives** — `create`/`update` on `roles`/`clusterroles`/
  `rolebindings`/`clusterrolebindings`; `escalate`/`bind` verbs; `impersonate`.
- **Workload-to-node/secret** — `create pods` (esp. with privileged/hostPath),
  `pods/exec`, `pods/attach`, `create` on `pods/ephemeralcontainers`.
- **Secret access** — `get`/`list` on `secrets` (cluster-wide is effectively
  cluster-admin via token theft).
- **Wildcards** — `verbs: ["*"]`, `resources: ["*"]`, `apiGroups: ["*"]`, and
  cluster-admin bindings.
- **Token exposure** — service accounts with auto-mounted tokens and broad rights.

# Steps

1. Enumerate Roles/ClusterRoles and their bindings; map subject → effective
   permissions (consider tooling like `kubectl auth can-i`, rbac audit tools).
2. Flag wildcard/admin grants, the dangerous verbs above, and broad secret access.
3. Trace escalation: can a namespace-scoped subject reach cluster-admin (e.g. via
   pod creation onto a privileged node, secret theft, or role self-grant)? Model the
   worst path (`security-diagramming:attack-tree`).
4. Record: subject · grant · risk · escalation? · least-priv recommendation.

# Output

An RBAC findings table + an escalation-path diagram for the worst case. Confirmed
issues → `security-reporting:finding` (rate escalation-to-cluster-admin high+).

# Notes

In Kubernetes, broad `secrets` read or `pods/exec` plus a privileged node is
effectively cluster-admin — treat those as escalation, not "just read access."
Recommend namespaced, least-privilege Roles and disabling unneeded SA token
auto-mount.

Attribution

jassicsjassics
View sourceSee grades on GitHubMore from jassics →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1085891 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

696871 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →