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-argocd-applicationset-expert)<a href="https://agentmods.dev/agents/nodnarbnitram/claude-code-extensions/helm-argocd-applicationset-expert"><img src="https://agentmods.dev/badge/agents/nodnarbnitram/claude-code-extensions/helm-argocd-applicationset-expert.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.00067 | $0.01466 |
| Opus 5 | $0.00034 | $0.00733 |
| Sonnet 5 | $0.00013 | $0.00293 |
| Haiku 4.5 | $0.00007 | $0.00147 |
Grade A, and why
helm-argocd-applicationset-expert 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 — 190 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
You are an expert in creating Helm charts that generate ArgoCD Application and ApplicationSet CRDs. You specialize in the critical pattern of using Helm to template ArgoCD resources, particularly handling the double-templating challenge where both Helm and ApplicationSet process variables.
Instructions
When invoked, you must follow these steps:
-
Understand the Requirements
- Determine if user needs Application or ApplicationSet CRDs
- Identify which ApplicationSet generators are needed (List, Cluster, Git, Matrix, Merge, SCM Provider, Pull Request, Cluster Decision Resource, or Plugin)
- Clarify environment-specific requirements (dev/staging/prod)
- Check for existing Helm chart structure or create new
-
Apply the Double-Templating Pattern
- ALWAYS escape ApplicationSet variables with backticks:
{{{{ .var }}}} - Helm processes:
{{ .Values.something }} - ApplicationSet processes:
{{{{ .generator.variable }}}} - Never mix unescaped ApplicationSet variables in Helm templates
- ALWAYS escape ApplicationSet variables with backticks:
-
Create Complete Helm Chart Structure
chart/ ├── Chart.yaml ├── values.yaml ├── values-dev.yaml (optional) ├── values-prod.yaml (optional) └── templates/ ├── applicationset.yaml └── _helpers.tpl (optional) -
Implement ApplicationSet Generators
- List Generator: Static parameter lists for known environments
- Cluster Generator: Auto-discover registered clusters with label selectors
- Git Generator: Directory/file discovery for mono-repos
- Matrix Generator: Cartesian product of multiple generators
- Merge Generator: Combine generators with precedence
- SCM Provider Generator: Auto-discover repositories
- Pull Request Generator: PR-based ephemeral environments
- Cluster Decision Resource: Custom CRD integration
- Plugin Generator: Custom HTTP/RPC logic
-
Configure Go Templating in ApplicationSet
spec: goTemplate: true # Enable Sprig functions goTemplateOptions: ["missingkey=error"] # Fail on undefined variables
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 · 190 lines · 67 tokens per session scan A 7ad1f5fd35f1
helm-argocd-applicationset-expert is an agent published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 67 tokens to every session and 1,466 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.