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/notque/vexjoy-agent/kubernetes-helm-engineergit clone --depth 1 https://github.com/notque/vexjoy-agentWrote 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/notque/vexjoy-agent/kubernetes-helm-engineer)<a href="https://agentmods.dev/agents/notque/vexjoy-agent/kubernetes-helm-engineer"><img src="https://agentmods.dev/badge/agents/notque/vexjoy-agent/kubernetes-helm-engineer.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 | $0.00000 | $0.00508 |
| Opus 5 | $0.00000 | $0.00254 |
| Sonnet 5 | $0.00000 | $0.00102 |
| Haiku 4.5 | $0.00000 | $0.00051 |
Grade A, and why
kubernetes-helm-engineer 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 5d 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Kubernetes Helm Engineer (Your Organization's Version)
This is a template for your organization-specific Kubernetes/Helm agent.
What to Customize
Replace the generic examples below with your actual:
- Internal repository paths
- Helm chart locations
- Service names
- Team conventions
Example Customizations
Your Helm Charts Location
# Generic version says: /path/to/helm-charts
# Your version:
cd /home/youruser/projects/infrastructure/helm-charts
Your Internal Services
# Generic version uses placeholder service names
# Your version - real services:
services:
audit: audit-service # Your audit service
metrics: prometheus # Your metrics service
logging: elasticsearch # Your logging service
Your Kubernetes Contexts
# Generic version: kubectl config use-context <context>
# Your version:
kubectl config use-context production-eu-west-1
kubectl config use-context staging-us-east-1
Your Namespace Conventions
# Generic version: kubectl -n <namespace>
# Your version:
kubectl -n platform-services
kubectl -n monitoring
kubectl -n audit-system
Instructions
- Copy this file to
.local/agents/kubernetes-helm-engineer.md - Replace all placeholders with your real values
- Add your organization's specific patterns and conventions
- When you need Kubernetes help, reference this file:
"Read .local/agents/kubernetes-helm-engineer.md and help me deploy"
Template Sections to Fill In
Your Helm Repository
helm repo add yourcompany https://charts.yourcompany.com
helm repo update
Your Common Helm Values
# values-production.yaml template
global:
environment: production
region: # YOUR_REGION
image:
registry: # YOUR_REGISTRY
pullPolicy: Always
resources:
requests:
memory: "256Mi"
cpu: "100m"
limits:
memory: "512Mi"
cpu: "500m"
Your Deployment Checklist
- Verify kubectl context is correct
- Check resource quotas in namespace
- Review values file for environment
- Run helm diff before upgrade
- Verify pods are healthy after 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.
- 5d ago First seen · 106 lines · 0 tokens per session scan A 61957247ea80
kubernetes-helm-engineer is an agent published in the GitHub repository notque/vexjoy-agent (419 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 508 tokens. 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 agents, from other repositories
devops-platform-engineer-lead
Never place secrets, credentials, tokens, PII, or production data in any field; reference affected files by redacted path only.
cap-project-architect
Use this agent when setting up new CAP projects, configuring deployment, implementing multitenancy, or designing application architecture. This agent specializes in project structure, configuration, and deployment patterns. Examples: "Initialize a new CAP project with Node.js and HANA" "Configure Cloud Foundry…
infra-deployment-auditor
Use proactively for Kubernetes, Terraform, production Docker Compose, release readiness, deployment scripts, preflight flows, and operator-facing documentation.
ciel-cloud-ops-guild
CIEL's elite cloud and DevOps guild. Specializes in AWS, GCP, Azure, K8s, Docker, and CI/CD automation.
cloud-security-agent
AWS/Azure/GCP security audit, S3 bucket enumeration, container image scanning, Kubernetes RBAC review, IaC misconfiguration detection. 4-phase workflow with approval gate.
infra-expert
Use this agent as a distinguished Infrastructure/K8s/SRE authority for peer-review-level infrastructure review, incident response, and GKE/GCP platform expertise. Covers Kubernetes deep internals, GKE-specific features, Istio service mesh, Terraform/IaC, GCP platform services, networking, cost engineering, and…