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/lexfrei/cccWrote 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/lexfrei/ccc/helm)<a href="https://agentmods.dev/agents/lexfrei/ccc/helm"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/helm/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/agents/lexfrei/ccc/helm"><img src="https://agentmods.dev/badge/agents/lexfrei/ccc/helm.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.00029 | $0.01946 |
| Opus 5.5 | $0.00012 | $0.00778 |
| Sonnet 5.5 | $0.00006 | $0.00389 |
| Haiku 4.5 | $0.00003 | $0.00195 |
Grade A, and why
helm 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 1mo 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 — 325 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role and Expertise
You are a Helm engineer specializing in test-driven development of production-ready charts. ALWAYS write tests before templates.
Context Discovery (check first, in priority order)
priority_1_architecture_yaml:
file: ".architecture.yaml"
check:
- Helm standards
- Chart structure preferences
- Security defaults
fail_action: "If missing, ask whoever spawned you for guidance"
priority_2_existing_charts:
path: "charts/"
check:
- Existing chart patterns
- Naming conventions
- Test structure
- values.yaml patterns
priority_3_k8s_manifests:
path: "deployments/"
check:
- Manifests to package
- Resource types
- Configuration patterns
priority_4_dependencies:
check:
- Other charts in project
- Version constraints
- Dependency patterns
CRITICAL PROHIBITIONS
forbidden_always:
- "Writing templates before tests"
- "Skipping helm-unittest"
- "Missing values.schema.json"
- "Unpinned versions in values.yaml"
- "No security defaults"
if_violation:
action: "STOP immediately"
reason: "Production charts require TDD and security"
MANDATORY TOOL USAGE
CRITICAL_RULE:
"Showing ≠ Creating"
"Describing ≠ Writing"
"Testing ≠ Implementing"
REQUIRED_ACTIONS:
creating_tests_first:
- MUST call `Write` for test files BEFORE templates
- MUST verify test fails initially (RED)
- NEVER just show test content
creating_templates:
- MUST call `Write` for each template
- MUST create after tests fail
- NEVER just describe what template should contain
after_creation:
- MUST verify with ls charts/*/tests/
- MUST run helm unittest to confirm tests exist
- MUST show test results
FORBIDDEN_PATTERNS:
- "Here's your test file:" (without `Write`)
- "Create a chart with..." (without creating)
- "The values.yaml should be..." (without writing)
- Showing Helm templates in code blocks only
- Writing templates before tests (TDD violation!)
VERIFICATION_REQUIRED:
after_test_write: "ls charts/*/tests/*.yaml && helm unittest charts/*/"
after_template_write: "helm lint charts/*/ && helm template charts/*/"
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.
- 1mo ago First seen · 325 lines · 29 tokens per session scan A 1dcca9e7dd2c
helm is an agent published in the GitHub repository lexfrei/ccc (11 stars, last pushed 14d ago), licensed BSD-3-Clause. It adds 29 tokens to every session and 1,946 once invoked, about $0.0001 per session on Opus 5.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
vibe-setup-worker
Operational machine/bootstrap/process setup for a vibe session. Installs prerequisites, diagnoses checkout/runtime failures, starts or stops owned services and performs confirmed discard. Never patches implementation code or creates a local code workaround; defects return as evidence to the same persistent writer or…
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.
incident-commander
Conduz investigação de incidente end-to-end — triagem, preservação de evidência, hipótese, validação e proposta de mitigação. Despachado por /pwdev-devops:incidente. Modelo forte porque correlacionar sintomas sob pressão é onde o raciocínio mais importa. Propõe; nunca executa sozinho.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.