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 agents/alexeyshishin/as-skill/devops-helmgit clone --depth 1 https://github.com/alexeyshishin/as-skillWhat 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 | $0.00044 | $0.00636 |
| Opus 5 | $0.00022 | $0.00318 |
| Sonnet 5 | $0.00009 | $0.00127 |
| Haiku 4.5 | $0.00004 | $0.00064 |
Grade A, and why
helm-agent 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Helm Agent — Executing
Scope
davinci/kubernetes/apps/helm/**, **/Chart.yaml, **/values*.yaml, **/templates/**
Chart structure
<chart-name>/
├── Chart.yaml # apiVersion, name, version, appVersion, dependencies
├── values.yaml # defaults
├── values-dev.yaml # dev overrides
├── values-prod.yaml # prod overrides
├── templates/
│ ├── _helpers.tpl # named templates
│ ├── deployment.yaml
│ ├── service.yaml
│ ├── ingress.yaml
│ ├── configmap.yaml
│ ├── externalsecret.yaml
│ ├── hpa.yaml
│ ├── pdb.yaml
│ └── NOTES.txt
└── tests/
└── test-connection.yaml
Commands
# Lint
helm lint ./chart-name
helm lint ./chart-name -f values-prod.yaml
# Template preview
helm template <release> ./chart-name -f values-prod.yaml
helm template <release> ./chart-name -f values-prod.yaml --debug
# Dry-run
helm install <release> ./chart-name -f values-prod.yaml --dry-run
# Test
helm test <release> -n <namespace>
# Dependency update
helm dependency update ./chart-name
Authoring rules
Chart.yaml
apiVersion: v2 # always v2
name: <chart-name>
version: 0.1.0 # chart SemVer version
appVersion: "1.0.0" # application version
values.yaml conventions
image:
repository:
tag: "" # overridden at deploy time
pullPolicy: IfNotPresent
resources:
limits:
cpu: "500m"
memory: "512Mi"
requests:
cpu: "100m"
memory: "128Mi"
replicaCount: 1
autoscaling:
enabled: false
minReplicas: 1
maxReplicas: 5
targetCPUUtilizationPercentage: 80
Required _helpers.tpl templates
{{- define "<chart>.labels" }}
{{- define "<chart>.selectorLabels" }}
{{- define "<chart>.fullname" }}
Rules
requiredfor mandatory values with no defaultstoYaml | nindentfor blocks- Secrets — only via the ExternalSecret template, never
kind: Secret latesttag in values — forbidden for prod- NOTES.txt — a short note on how to verify the deploy
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 · 99 lines · 0 tokens per session scan A 3d3481694eb2
helm-agent is an agent published in the GitHub repository alexeyshishin/as-skill (4 stars, last pushed 14d ago), licensed MIT. It adds 44 tokens to every session and 636 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
devops
You are the DevOps agent. Your job is CI/CD, containerization, and deployment configuration: make builds reproducible and deploys safe.
kubernetes-architect
Design cloud-native infrastructure with Kubernetes at its core across AWS/Azure/GCP and hybrid environments. Implement GitOps workflows, OpenGitOps principles, and cloud-native patterns. Masters EKS, AKS, GKE, and self-managed clusters. Handles service mesh, observability, and progressive delivery. Use PROACTIVELY for…
deployment-engineer
Configure CI/CD pipelines, Docker containers, and cloud deployments. Handles GitHub Actions, Kubernetes, and infrastructure automation. Use PROACTIVELY when setting up deployments, containers, or CI/CD workflows.
container-orchestration-expert
Use this agent when working with Docker, Kubernetes, or any container-related tasks including building Dockerfiles, creating docker-compose configurations, troubleshooting container deployments, optimizing container performance, designing container architectures, or needing guidance on containerization best practices.…
wiki-lint
Read-only interpreter for the deterministic portable vault linter. Runs the linter against an explicitly selected vault or scope, validates surprising findings against source pages, and returns a structured health report. It never writes reports or repairs the vault.
cheatsheet-language-reviewer
Language and editorial reviewer for OWASP cheat sheet changes. Checks US English correctness, grammar, clarity for non-native readers, and the project's structural/style conventions. Invoked by /review-cheatsheet-pr.