analyzing-kubernetes-audit-logs

analyzing-kubernetes-audit-logs is a skill for Claude Code from plurigrid/asi. It costs 71 tokens per session (474 once invoked), scanned A, original, MIT.

A guide to reading Kubernetes API audit logs, which record requests made to a Kubernetes cluster. It focuses on events that may show stolen access, privilege increases, or sensitive data access.

In plain words
What is it for?
Use it to investigate a possibly compromised cluster, look for pod shell access, secret reads, RBAC changes, privileged pods, and anonymous API requests, or improve SIEM monitoring.
Why use it?
It helps investigators spot suspicious cluster activity and turn repeated log patterns into detection rules. Kubernetes is a system for running containers and services, so these logs show who requested changes or access.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the asi plugin — 56 skills shipped together

Good fit Use it to investigate a possibly compromised cluster, look for pod shell access, secret reads, RBAC changes, privileged pods, and anonymous API requests, or improve SIEM monitoring.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/plurigrid/asi/analyzing-kubernetes-audit-logs
Install

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.

Any agent
npx skills add plurigrid/asi --skill analyzing-kubernetes-audit-logs
Clone the repo
git clone --depth 1 https://github.com/plurigrid/asi

Made for: Claude Code.

Or install asi, the plugin that ships this one along with the rest of its 56 skills.

Wrote 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.

agentmods badge for analyzing-kubernetes-audit-logs

README.md
[![agentmods](https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-kubernetes-audit-logs/github.svg)](https://agentmods.dev/skills/plurigrid/asi/analyzing-kubernetes-audit-logs)
Your own site
<a href="https://agentmods.dev/skills/plurigrid/asi/analyzing-kubernetes-audit-logs"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-kubernetes-audit-logs/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.

agentmods 80×15 button for analyzing-kubernetes-audit-logs

Your own site · 80×15
<a href="https://agentmods.dev/skills/plurigrid/asi/analyzing-kubernetes-audit-logs"><img src="https://agentmods.dev/badge/skills/plurigrid/asi/analyzing-kubernetes-audit-logs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 474 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00071 $0.00474
Opus 5 $0.00036 $0.00237
Sonnet 5 $0.00014 $0.00095
Haiku 4.5 $0.00007 $0.00047

Measured 8d ago against content hash 0c5e89303d19, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

analyzing-kubernetes-audit-logs 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 8d 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.

Origin

Copies of this mod

5 near-identical copies found in the catalogue:

plugins/asi/skills/analyzing-kubernetes-audit-logs/SKILL.md · 65 lines

What it actually says

Analyzing Kubernetes Audit Logs

When to Use

  • When investigating security incidents that require analyzing kubernetes audit logs
  • When building detection rules or threat hunting queries for this domain
  • When SOC analysts need structured procedures for this analysis type
  • When validating security monitoring coverage for related attack techniques

Prerequisites

  • Familiarity with container security concepts and tools
  • Access to a test or lab environment for safe execution
  • Python 3.8+ with required dependencies installed
  • Appropriate authorization for any testing activities

Instructions

Parse Kubernetes audit log files (JSON lines format) to detect security-relevant events including unauthorized access, privilege escalation, and data exfiltration.

import json

with open("/var/log/kubernetes/audit.log") as f:
    for line in f:
        event = json.loads(line)
        verb = event.get("verb")
        resource = event.get("objectRef", {}).get("resource")
        user = event.get("user", {}).get("username")
        if verb == "create" and resource == "pods/exec":
            print(f"Pod exec by {user}")

Key events to detect:

  1. pods/exec and pods/attach (shell into containers)
  2. secrets access (get/list/watch)
  3. clusterrolebindings creation (RBAC escalation)
  4. Privileged pod creation
  5. Anonymous or system:unauthenticated access

Examples

# Detect secret enumeration
if verb in ("get", "list") and resource == "secrets":
    print(f"Secret access: {user} -> {event['objectRef'].get('name')}")
Changes

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.

  1. 8d ago First seen · 65 lines · 71 tokens per session scan A 0c5e89303d19

Subscribe to this mod's changes

analyzing-kubernetes-audit-logs is a skill published in the GitHub repository plurigrid/asi (62 stars, last pushed 2mo ago), licensed MIT. It adds 71 tokens to every session and 474 once invoked, about $0.0004 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-09-03.

Related

Other skills, from other repositories

analyzing-kubernetes-audit-logs

Use when parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM…

oyi77/1ai-skills · 72 tokens

analyzing-kubernetes-audit-logs

Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.

pinkpixel-dev/skills-collection-1 · 71 tokens

analyzing-kubernetes-audit-logs

Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.

marysatasselshaped667/skills-collection-1 · 71 tokens

analyzing-kubernetes-audit-logs

Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.

Mikaru0Mystic/sectinel · 71 tokens

analyzing-kubernetes-audit-logs

Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.

xalgorix/xalgorix · 71 tokens

analyzing-kubernetes-audit-logs

Parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM detection rules.

autohandai/community-skills · 71 tokens