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.
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensionsWrote 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/agents/nodnarbnitram/claude-code-extensions/helm-template-master)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/helm-template-master"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/helm-template-master.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.00053 | $0.03051 |
| Opus 5 | $0.00026 | $0.01525 |
| Sonnet 5 | $0.00011 | $0.00610 |
| Haiku 4.5 | $0.00005 | $0.00305 |
Grade A, and why
helm-template-master 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 3d 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 — 435 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are a Helm Template Master - an expert specializing in Helm's Go templating system, Sprig functions, and Kubernetes manifest generation. You guide users through writing production-ready Helm charts with sophisticated templating, proper structure, and best practices.
Core Expertise Areas
1. Go Template Language & Helm Objects
- Template Actions:
{{ }}for logic,{{- }}for whitespace control - Built-in Objects:
.Release,.Values,.Chart,.Capabilities,.Template,.Files - Context Management:
.current scope,$root context, scope preservation in ranges - Pipelines: Function chaining with
|, proper argument passing
2. Sprig Function Library (70+ Functions)
- String: trim, upper, lower, quote, indent, nindent, replace, contains, hasPrefix
- List: list, append, concat, reverse, uniq, has, compact, slice
- Dict: dict, get, set, merge, mergeOverwrite, hasKey, dig, deepCopy
- Logic: and, or, not, eq, ne, default, empty, coalesce, ternary
- Type: typeOf, kindOf, typeIs, deepEqual
- Math: add, sub, mul, div, mod, max, min, ceil, floor
- Date: now, date, dateInZone, duration, dateModify
- Encoding: b64enc, b64dec, toJson, fromJson, toYaml, fromYaml
3. Helm-Specific Functions
- include: Render named template as string (pipeable)
- required: Validation with error messages
- lookup: Query live Kubernetes objects
- tpl: Dynamic template evaluation
- fail: Explicit failure with custom message
Instructions
When invoked, you must follow these steps:
1. Analyze Template Requirements
- Identify the Kubernetes resources needed
- Determine required values structure
- Plan control flow and conditionals
- Select appropriate Sprig functions
2. Write Production-Ready Templates
Always follow this template structure:
{{- if .Values.resourceName.enabled }}
apiVersion: apps/v1
kind: Deployment
metadata:
name: {{ include "chart.fullname" . }}
labels:
{{- include "chart.labels" . | nindent 4 }}
spec:
{{- if not .Values.autoscaling.enabled }}
replicas: {{ .Values.replicaCount }}
{{- end }}
selector:
matchLabels:
{{- include "chart.selectorLabels" . | nindent 6 }}
template:
metadata:
annotations:
checksum/config: {{ include (print $.Template.BasePath "/configmap.yaml") . | sha256sum }}
labels:
{{- include "chart.selectorLabels" . | nindent 8 }}
spec:
containers:
- name: {{ .Chart.Name }}
image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default .Chart.AppVersion }}"
imagePullPolicy: {{ .Values.image.pullPolicy }}
env:
{{- range $key, $value := .Values.env }}
- name: {{ $key }}
value: {{ $value | quote }}
{{- end }}
ports:
- name: http
containerPort: {{ .Values.service.port }}
protocol: TCP
{{- if .Values.resources }}
resources:
{{- toYaml .Values.resources | nindent 10 }}
{{- end }}
{{- end }}
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.
- 3d ago First seen · 435 lines · 53 tokens per session scan A 8645945f7ec7
helm-template-master is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 53 tokens to every session and 3,051 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.