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 agentmods add commands/infraspecdev/tesseract/review-helmgit clone --depth 1 https://github.com/infraspecdev/tesseractWrote 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/infraspecdev/tesseract/review-helm)<a href="https://agentmods.dev/commands/infraspecdev/tesseract/review-helm"><img src="https://agentmods.dev/badge/commands/infraspecdev/tesseract/review-helm.svg" alt="Measured on agentmods" 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.00025 | $0.00709 |
| Opus 5 | $0.00013 | $0.00354 |
| Sonnet 5 | $0.00005 | $0.00142 |
| Haiku 4.5 | $0.00003 | $0.00071 |
Grade A, and why
review-helm 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 2d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm Chart Review
Run a comprehensive review of a Helm chart covering chart structure, template best practices, and K8s security/operational issues in rendered templates.
Usage
/review-helm [path]
Paths
Writes registry-tracked paths under {review_dir} = {output_dir}/{feature}/reviews/code/{date}{_counter} (review_type=code, agents=helm-structure / k8s-security / 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
- Detect Helm chart at the given path (or current working directory):
- Look for
Chart.yamlfile - If not found, inform the user and exit
- Look for
- Invoke the following skills:
shield:kubernetes:helm-review— chart structure and best practicesshield:kubernetes:security-audit— security issues in templatesshield:kubernetes:operational-review— operational issues in templates
- If deprecated K8s API versions found in templates, recommend
deprecation-check-and-upgrade - Aggregate findings, deduplicate, sort by severity
- 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/
├── helm-structure.md ← {review_detailed} (agent=helm-structure)
├── k8s-security.md ← {review_detailed} (agent=k8s-security)
└── k8s-operations.md ← {review_detailed} (agent=k8s-operations)
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.
- 2d ago First seen · 56 lines · 25 tokens per session scan A 54262085f675
review-helm is a command published in the GitHub repository infraspecdev/tesseract (5 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 709 once invoked, about $0.0001 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.
Other commands, from other repositories
create-docker-mcp-tunnel
Stand up an Anthropic MCP tunnel locally with Docker Compose so Claude can call a private MCP server (manual-credentials quickstart).
cisco-isovalent-platform-setup
Install the Isovalent platform on Kubernetes (Cilium CNI, Hubble observability, Tetragon eBPF runtime security) in either OSS or Enterprise edition. Renders Helm values and install/upgrade scripts; this is the platform install prerequisite for the Splunk Observability + Splunk Platform integration done by…
build-agent
Build Docker images for Golden Armada agents.
application-crud
Command "application-crud" from tranfu-labs/tranfu-skills, covering application crud 操作速查 (private-github-app + dockercompose), token 原文永不写进命令字符串, 永远只引用 $coolifyapitoken, 列出所有 application (ad-hoc 排障用), 创建 application (private-github-app + dockercompose) and post 常见 4xx.
sandbox-destroy
Tear down a sandbox box — remove its container and named volume. --keep-volume leaves the volume; with no id, prune reclaims any leaked ca.sandbox=1-labeled object. Cached images are retained.
create-operator
Guided workflow to create a complete Kubernetes CRD operator.