review-k8s

review-k8s is a command for Claude Code from infraspecdev/tesseract. It costs 17 tokens per session (875 once invoked), scanned A, original, MIT.

A command for reviewing Kubernetes manifests, which are YAML files describing resources deployed to a Kubernetes cluster.

In plain words
What is it for?
Run it on Kubernetes manifests to assess security, resource cost, operational readiness, and, when relevant, Kustomize configuration.
Why use it?
It finds security, cost, and operational risks before those deployment settings are used in a cluster.

Command for Claude Code

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

Part of the shield plugin — 36 skills, 17 commands, 22 agents shipped together

Good fit Run it on Kubernetes manifests to assess security, resource cost, operational readiness, and, when relevant, Kustomize configuration.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/infraspecdev/tesseract/review-k8s
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.

Clone the repo
git clone --depth 1 https://github.com/infraspecdev/tesseract

Made for: Claude Code.

Or install shield, the plugin that ships this one along with the rest of its 36 skills, 17 commands, 22 agents.

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 review-k8s

README.md
[![agentmods](https://agentmods.dev/badge/commands/infraspecdev/tesseract/review-k8s/github.svg)](https://agentmods.dev/commands/infraspecdev/tesseract/review-k8s)
Your own site
<a href="https://agentmods.dev/commands/infraspecdev/tesseract/review-k8s"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/review-k8s/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 review-k8s

Your own site · 80×15
<a href="https://agentmods.dev/commands/infraspecdev/tesseract/review-k8s"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/review-k8s.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 875 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.00017 $0.00875
Opus 5.5 $0.00007 $0.00350
Sonnet 5.5 $0.00003 $0.00175
Haiku 4.5 $0.00002 $0.00088

Measured 1mo ago against content hash 17082030ae74, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-k8s 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 1mo 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.

shield/commands/review-k8s.md · 67 lines

How it starts

The opening of the file, as written. The whole thing — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Kubernetes Review

Run a comprehensive review of Kubernetes manifests covering security, cost optimization, and operational readiness.

Usage

/review-k8s [path]

Paths

Writes registry-tracked paths under {review_dir} = {output_dir}/{feature}/reviews/code/{date}{_counter} (review_type=code, agents=k8s-security / k8s-cost / k8s-operations — one {review_detailed} per skill). See shield/schema/output-paths.yaml and the counter-resolution rule in /review. changes.md is a side-artifact.

Behavior

  1. Detect K8s manifest files at the given path (or current working directory):
    • Look for YAML files containing apiVersion: and kind: with K8s resource types
    • If no K8s manifests found, inform the user and exit
    • If kustomization.yaml found, also invoke shield:kubernetes:kustomize-review
  2. Invoke the following skills in parallel:
    • shield:kubernetes:security-audit
    • shield:kubernetes:cost-review
    • shield:kubernetes:operational-review
  3. Dispatch shield:platform-engineer agent in all three modes (security, cost, operational) in parallel
  4. If deprecated APIs found by any skill, run shield:kubernetes:deprecation-check-and-upgrade for upgrade guidance
  5. Aggregate findings, deduplicate, sort by severity
  6. Present unified findings to the user

Output Path

First, find the project root by locating .shield.json (check current directory, then parent directories). Read .shield.json to get output_dir (default: docs/shield). Determine {feature} (current feature directory name; if none exists yet, derive from current branch or story context + -YYYYMMDD). Resolve {date}{_counter} per the counter rule in /review (today's ISO date in YYYY-MM-DD format; empty _counter for first same-day run, _2/_3/... otherwise).

Write findings under {review_dir} = {output_dir}/{feature}/reviews/code/{date}{_counter}/:

{review_dir}/
├── summary.md              ← {review_summary}
├── changes.md              ← applied-fixes log (side-artifact)
└── detailed/
    ├── k8s-security.md     ← {review_detailed} (agent=k8s-security)
    ├── k8s-cost.md         ← {review_detailed} (agent=k8s-cost)
    └── k8s-operations.md   ← {review_detailed} (agent=k8s-operations)

Read the full file on GitHub · 67 lines

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. 1mo ago First seen · 67 lines · 17 tokens per session scan A 17082030ae74

Subscribe to this mod's changes

review-k8s is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 3mo ago), licensed MIT. It adds 17 tokens to every session and 875 once invoked, about $0.0001 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.