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 instructions/duyet/charts/claude-mdgit clone --depth 1 https://github.com/duyet/chartsWrote 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/instructions/duyet/charts/claude-md)<a href="https://agentmods.dev/instructions/duyet/charts/claude-md"><img src="https://agentmods.dev/badge/instructions/duyet/charts/claude-md.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.03153 | $0.03153 |
| Opus 5 | $0.01577 | $0.01577 |
| Sonnet 5 | $0.00631 | $0.00631 |
| Haiku 4.5 | $0.00315 | $0.00315 |
Grade A, and why
charts CLAUDE.md 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 — 503 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - Project Philosophy & Development Guide
"Simplicity is the ultimate sophistication." - Leonardo da Vinci
This document captures the soul of this Helm charts repository. Read this first before contributing.
The Vision
This repository is a collection of production-ready Helm charts that guide users toward secure, scalable deployments while maintaining the flexibility to customize for their needs.
We don't just make charts that work—we make charts that are inevitable. Every configuration option should feel natural. Every default should be sensible. Every template should be elegant.
Core Principles
1. Simplicity Without Losing Power
The best solutions are simple but not simplistic. Our charts should:
- Provide sensible defaults that work out of the box
- Expose configuration for production requirements
- Hide complexity without limiting capability
- Make the common case easy and the advanced case possible
Example: Default to 1 replica for simplicity, but always make replicaCount configurable for production scaling.
2. Consistency is Kindness
When users move between charts in this repository, they should feel at home. This means:
- Uniform
values.yamlstructure across all charts - Consistent naming conventions
- Shared patterns for common features (service accounts, security contexts, etc.)
- Modern, standardized template syntax (
nindent, notindent | trim)
Why it matters: Cognitive load is a user experience issue. Consistency reduces friction.
3. Security by Default
Security isn't optional. Every chart should:
- Use non-root users by default where possible
- Support (and encourage) security contexts
- Never hard-code secrets
- Always support
existingSecretpatterns - Provide resource limits as defaults
Philosophy: Make the secure path the easy path.
4. Production-Ready from Day One
These charts aren't experiments. They're tools for running real workloads. This means:
- Config changes trigger automatic pod restarts (via checksum annotations)
- Health checks are included and sensible
- Resource limits prevent runaway processes
- Support for PodDisruptionBudgets on critical services
- Clear NOTES.txt with post-installation guidance
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 · 503 lines · 3,153 tokens per session scan A 416d191cb35b
charts CLAUDE.md is an instructions file published in the GitHub repository duyet/charts (19 stars, last pushed 7d ago), licensed MIT. It adds 3,153 tokens to every session, about $0.0158 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 instructions, from other repositories
helm-zabbix CLAUDE.md
Instructions for zabbix-community/helm-zabbix, covering claude.md, repository overview, common commands, architecture and template/value organization.
k8e AGENTS.md
Instructions for xiaods/k8e, covering agents.md, project overview, architecture (big picture), key architectural flows and building.
openclaw-kubernetes AGENTS.md
Instructions for feiskyer/openclaw-kubernetes, covering agents.md, links, development commands, lint the chart against all values files and render templates to verify correctness (output discarded).
terraform-hcloud-kube-hetzner AGENTS.md
AGENTS.md instructions for mysticaltech/terraform-hcloud-kube-hetzner, a project described as: Optimized and Maintenance-free Kubernetes on Hetzner Cloud in one command!
kubara CLAUDE.md
Instructions for kubara-io/kubara, a project described as: kubara is a single binary CLI tool written in Go providing a lightweight framework for bootstrapping Kubernetes platforms with production-proven best practices.
openclaw-kubernetes CLAUDE.md
Instructions for feiskyer/openclaw-kubernetes, covering claude.md, links, development commands, lint the chart against all values files and render templates to verify correctness (output discarded).