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 skills add tahirraufkeeyu/software-development-agent-stack--sdas --skill helm-chartsgit clone --depth 1 https://github.com/tahirraufkeeyu/software-development-agent-stack--sdasWrote 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/skills/tahirraufkeeyu/software-development-agent-stack--sdas/helm-charts)<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/helm-charts"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/helm-charts/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.
<a href="https://agentmods.dev/skills/tahirraufkeeyu/software-development-agent-stack--sdas/helm-charts"><img src="https://agentmods.dev/badge/skills/tahirraufkeeyu/software-development-agent-stack--sdas/helm-charts.svg" alt="Reviewed on agentmods" width="80" 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.00065 | $0.03546 |
| Opus 5 | $0.00032 | $0.01773 |
| Sonnet 5 | $0.00013 | $0.00709 |
| Haiku 4.5 | $0.00006 | $0.00355 |
Grade A, and why
helm-charts 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 10d 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 — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
When to use
- A service is moving from
kubectl apply -for kustomize to Helm. - An existing chart has drifted into copy-paste per environment and needs consolidation.
- Generating a library of internal charts for consistent service shape.
Do not use this skill when the answer is Kustomize + overlays (simpler for small apps) or Argo CD ApplicationSet without templating needs.
Inputs
chart_name— matches the service name (checkout-api).app_version— app semver (1.4.2). Chart version (0.x.y) is independent and tracks chart changes.image— default repository, e.g.ghcr.io/acme/checkout-api.port— container port and service port (e.g.8080).ingress_host— optional, e.g.checkout.staging.acme.example.enable_hpa— bool, defaulttruefor anything that handles user traffic.secrets— list of keys the app reads from env; the chart emitsExternalSecretor reads from a namedSecret.configmap— map of non-secret config keys.namespace— default namespace name.
Outputs
- A chart directory
charts/<chart_name>/containing:Chart.yaml,values.yaml,values-staging.yaml,values-prod.yaml.templates/with_helpers.tpl,deployment.yaml,service.yaml,ingress.yaml,configmap.yaml,hpa.yaml,serviceaccount.yaml,poddisruptionbudget.yaml,NOTES.txt..helmignore,README.md(generated withhelm-docs).ci/with sample test values for chart-testing (ct).
Tool dependencies
helm>= 3.12.kubeconformand/orkubevalfor schema validation.helm-docsfor README generation.chart-testing(ct) for lint-install-upgrade tests in CI.- Optional:
helm diffplugin for live diffing.
Procedure
0. Detect the stack
Confirm Helm + Kubernetes is the packaging system the user wants before scaffolding:
helm version --short 2>/dev/null # Helm 3.x installed?
kubectl config current-context 2>/dev/null # K8s cluster reachable?
ls charts/ helm/ 2>/dev/null # existing Helm charts?
ls kustomize/ overlays/ 2>/dev/null # Kustomize instead?
ls terraform/ main.tf 2>/dev/null | head # Terraform-managed K8s resources?
find . -maxdepth 2 -name 'Chart.yaml' 2>/dev/null # existing chart in this repo?
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.
- 10d ago First seen · 395 lines · 65 tokens per session scan A c5c0b674c60d
helm-charts is a skill published in the GitHub repository tahirraufkeeyu/software-development-agent-stack--sdas (18 stars, last pushed 4mo ago), licensed MIT. It adds 65 tokens to every session and 3,546 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-08-30.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.